Add additional ray trace API

[TonytheMacaroni]

Supersedes #11166.

• Adds overloads to World#rayTrace and World#rayTraceBlocks, as well as the method PositionedRayTraceConfigurationBuilder#blockCollisionMode, that take a BlockCollisionMode instead of the boolean ignorePassableBlocks to determine block collisions.
• Add FluidCollisionMode.WATER.
• Remove outdated javadocs on World#rayTrace, World#rayTraceBlocks, PositionedRayTraceConfigurationBuilder#fluidCollisionMode, and PositionedRayTraceConfigurationBuilder#ignorePassableBlocks that mention caveats with portal blocks and fluids that no longer exist. Portal blocks are always considered 'passable', and the value of ignorePassableBlocks has no effect on fluid collisions.

[notTamion]

If we are going to expose water we should add lava to the nms enum and add it here aswell

[notTamion]

Feels kinda weird to expose this one, as i think it would feel pretty random to someone using the API. And its only really there for internal Falldamage calculations

[Machine-Maker]

yeah, you should be able to replicate it yourself with the predicate anyways right?

[TonytheMacaroni]

Kinda - for some reason, this mode always uses a full block shape, instead of the actual collision shape of the block. I do agree that I don't see too much of a point of keeping it, beyond perhaps making replicating fall damage calculations in API easier to do. I don't see much of a point to not include it, though.

[notTamion]

It makes the enums we have in the API seem rather random and odly specific, same thing for the WATER, LAVA Review i left. If this uses a collision mode (full block shape) we don‘t otherwise have in the api then we should instead expose that one without the fall damage filtering part, that seems a lot more useful.

[lynxplay]

Generally am also on the side to expose a much as we need, as little as we can.

Overexposing internals for the sake of exposing them just makes your life harder when things change.