Fix floating point math

[BenjaminBrienen]

Objective

• Fixes bevy_color's operations are not stable across all hardware due to use of trigonometric float methods #15236

Solution

• Use bevy_math::ops instead of std floating point operations.

Testing

• Did you test these changes? If so, how?
  Unit tests and cargo run -p ci -- test

• How can other people (reviewers) test your changes? Is there anything specific they need to know?
  Execute cargo run -p ci -- test on Windows.

• If relevant, what platforms did you test these changes on, and are there any important ones you can't test?
  Windows

Migration Guide

• Not a breaking change
• Projects should use bevy math where applicable

[BenjaminBrienen]

This is incomplete because the test still fails :)

[IQuick143]

The -ln needs fixing, I left some other comments, but those aren't all that blocking.

Someone else please take a thorough look, cause there's a lot of code touched so I may have missed smth.

[BenjaminBrienen]

This is in a good state for now, but I'm waiting for conclusive feedback on exactly how explicit we should make the calls to bevy_math trig functions, especially in documentation and examples.

[BenjaminBrienen]

If anyone would like to suggest a different name for bevy_math::ops before it is made public, now is a good time. To me, ops kind of implies the traits like Add and Mul (for bevy, maybe instead for matrices and vector operations).

[alice-i-cecile]

ops is fine IMO :)

[alice-i-cecile]

This is in a good state for now, but I'm waiting for conclusive feedback on exactly how explicit we should make the calls to bevy_math trig functions, especially in documentation and examples.

Stick it in the prelude, but use only the method names please.

[IQuick143]

Oh wow, this ended up being quite an undertaking, props for the work.