♻️ Rename all `rawOp` functions to `_op`?

[Vectorized]

trafficstars

The problem with prefixing it with "unsafe" or "raw" makes stuff super verbose.

And results in inconsistencies like toWadUnsafe vs unsafeMulWad; which I understand is because unsafeToWad just sounds werid.

The _op nomenclature has been used in SIMD intrinsics like _mm256_xor, and feels more natural.

With this renaming, we can have stuff like _expWad, _lnWad, without feeling awkward.

Still, there are some advantages of "raw" prefix:

• Auditoors immediately know it's raw.
• Easy to codeslaw. I can track down who are using Solady's FixedPointMathLib.

I'll probably leave this up for a few weeks before deciding.

Most probably will stick to no change.

[z0r0z]

I don't like safe and similar that want to add some semantics but not super verifiable (so, it's like "why").

++ on _op or similar more functional term.