[OoT] When exporting collision, check for degenerate triangles

[Thar0]

Degenerate triangles (triangles with close to 0 area, where all 3 vertices lie on or close to the same line) cause a crash during collision checking due to the assert at https://github.com/zeldaret/oot/blob/eb5dac74d6435baf85ced9158d3ff915ba8872ca/src/code/z_bgcheck.c#L751

When exporting the collision mesh, checking for these kinds of triangles and doing any of

• Skipping exporting them, so they don't end up in game (but potentially creating very tiny holes in the mesh)
• Warning about them on export, telling users there are degenerate triangles that need to be removed
• Erroring on export, telling users there are degenerate triangles that need to be removed

would be preferable to the current situation where they are exported without issue, leading to users often encountering this crash once they're in-game.

[Reonu]

I think a combination of 1 and 2 is the best. Skip them AND warn about them so that the user still knows that there's an issue with the model

Something like: "Export successful, however, X degenerate collision triangles have been detected and skipped. Please check your collision mesh."

[Yanis002]

I chose to implement reonu's suggestion in the PR, when exporting collision now it should skip the bad tris and throw a warning in the logs with the mesh object's name and its assigned material's name (to help figuring out which triangle)