Incorrect terminology regarding block states

Bedrock 1.20.30 changed some of the terminology relevant to blocks. Specifically, the block_property query was renamed to block_state. Parts of the scripting API and custom block JSON schemas were also updated in the same way. This was a mistake! property is the correct term here, and using the wrong term risks disparity and introducing confusion!

Let's use a furnace as an example. A furnace block has two relevant attributes: "facing" and "lit". There are 4 possible facing values and 2 possible lit values, so a total of 8 combinations. Now, we need two terms to describe, respectively, these individual attributes, and a fully formed block with values for each.

Java Edition, pioneering these concepts years ago, selected such terms. "facing" and "lit" are properties, the fully formed block is a block state. This precedent goes back years, is consistent, and evidence for it can be found everywhere in Java Edition.

• In resource packs, the blockstates folder maps blocks to models.

• In structure files, palette entries have a Properties compound for property values.

• The block NBT for an enderman's held block is called carriedBlockState, containing a block name and Properties compound for property values.

• The blocks.json report enumerates possible values for each blocks' properties in the properties key, then lists every combination in the states list, each of which describes the particular properties in its own properties map.

These terms have entered into community vernacular and are well-understood.

Bedrock decided to call a fully formed block a "permutation". This appears in several, relatively newer APIs and schemas. Although this differs from the established terminology, it's a fitting and unambiguous word with no competing definition.

Until 1.20.30, Bedrock agreed with the established terminology by calling properties properties. However, this change began referring to them as states. This is very confusing!! Not only does it break the established tradition, it uses a term that means something completely different! Players and creators coming from Java are now faced with a very nasty overloaded term, when just a few updates ago there was no such problem.

For the sake of parity and consistent, established and understood vernacular, please return the terminology from state to property, and ideally from permutation to state.