[TS] Delete VertexRange, use isTranslucent, fix partition tree sorting on geometry with negative dot products

[douira]

• Delete VertexRange as since the introduction of the translucency sorting system its first offset field wasn't getting used anymore. It can simply be calculated on the fly as a prefix sum. Currently missing vertex ranges are replicated as -1 lengths which are distinct from a length of zero. I don't know if this is actually necessary or if we can just use a zero length as the default.
• Use the isTranslucent method on terrain render passes and materials instead of checking equality
• Fix a crash related to translucency sorting that happened during the initial sort in the meshing task. This bug was triggered when a certain model (I don't know which one) on MCC Island was being sorted. Importantly, it extended outside of the chunk so that the dot products of its quads were negative with the axes. The partition tree building algorithm incorrectly handled negative dot products and produced a partition tree with duplicate nodes, which in turn led to a buffer overflow since too many quad indexes were being written.
• Fixed floatToComparableInt to actually be correct, it doesn't seem to have been correct previously.

[IMS212]

Would it make sense to remove the TS option from settings now, rather than later?

[douira]

I don't know if a setting is necessary. If we don't have to have it, we should remove it before release. Maybe keeping it as a setting in the config file only is enough. However, for debugging TS issues it's helpful if it can be disabled as a comparison. Then again, we can also send them a build with the setting and/or it disabled by default.

[jellysquid3]

I think we'll get rid of it (or put it behind a developer option) before release. But it's not relevant for this pull request.