more aggressive rust refactoring

[Random-Scientist]

this codebase will drive me insane but i'm too stubborn to go to sleep
the great de-nalgebrification.

• Use glam{x} {D, I}Vec3 as the canonical vector types
• as a consequence of the above, collapse a huge amount of manual implementations of vector arithmetic to vector methods/overloads
• pass vectors internally as vectors instead of constantly un and repacking them (rust won't punish you for wrapping your arguments in nice types)

[Random-Scientist]

before marking this as ready for review i'll go over the diff myself and make sure i got all the operator precedences right 💀

[Random-Scientist]

yep... got hit by an operator precedence bug in get_overlapping_nodes. I think that's the only one (at least, everything seems to work now when i mess around ingame, and i went over the changes pretty carefully in my second pass).

[tazercopter]

sounds like I need to look at this for #125

[ryanhcode]

we've added a CLA now btw, the workflow should update on the next commit

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ Random-Scientist
❌ github-actions[bot]
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[CherrieTheShifter]

Yes This