(extensions.decompile) Include TriColl meshes when decompiling Titanfall Engine maps

[snake-biscuits]

Now possible thanks to the extensions.geometry refactor & utils.physics:

• Standardising geometry extraction & processing #151
• Create a utils submodule to pull tools out of branches #162

The Plan

Once all CMBrushes are converted, grab TriCollHeaders
Use bounds & TextureData index to match rendered meshes to TriColl
misc_model gets broken down differently between the 2 systems

We might should be able to match Meshes against CM_Primitives based on bounds
Maybe some function w/ MeshBounds & Physics.AABB

[snake-biscuits]

TODO: copy the sp_training tree test run from discord

[snake-biscuits]

Need functions for matching geometry.Polygon against TricollTriangle
Set of indexed VERTICES would be faster

Would be interesting to know how winding directions compare

[snake-biscuits]

While digging around in sp_training I noticed a lot of _bm material TriColl tiles w/ 81 vertices & 128 triangles
Pretty clearly displacements, no sign of the origin brushes though (makes sense, they have no collision

Would be neat to decompile these into a .vmf, but idk how to automate that
Could make make an interactive decompiler where I can inspect and tag tricoll as displacements
sp_training has a nice grid of grass tiles, but other maps might not be so nice.