New block syntax requires literal empty state "[]", breaks Java parity

The issue

The new command block state syntax is now mandatory. Aside from the syntax already not matching Java (MCPE-112938), there is an additional issue. The block state part is its own argument, instead of being part of the block argument. As a result, this simple command produces a syntax error:

/setblock ~ ~ ~ air destroy

Instead, you are forced to type

/setblock ~ ~ ~ air[] destroy

This does not match Java Edition, in which the first command works fine. Requiring an empty state argument is redundant and confusing. The block and state should be two halves of a single argument to be compatible with Java Edition syntax, which is well-known since 1.13.