ensure numbers where we expected booleans parse correctly.

[456dev]

Boolean.parseBoolean expects the literal "true", which doesn't match the number 1.

The fix is to parse "1" as truthy, and all other values as falsy, like Boolean.parseBoolean() does.

fixes PaperMC/Velocity#1286

I'm assuming its meant to accept "1" as valid, seeing as it was specifically peeking for Numbers.
In velocity at least, "1" in json is emitted by the nbt component converter, from bytes

[456dev]

Oh, looks like it might be intentional, if there is a test for it.

does that just make this velocities problem?

[zml2008]

I think this is a format change from since component serialization started using Codecs? so it's a case of adventure's tests being outdated against the newly changed spec.

[456dev]

I'm still not 100% sure if this should change, as looking at the codecs etc, the vanilla jsonOps only parses / emits standard json bools, so this is more permissive than how minecraft behaves with json.
(only nbt ops parses bools using bytes i think)