Cubic splines overhaul

[JohnTheCoolingFan]

Objective

Improve the bevy::math::cubic_splines module by making it more flexible and adding new curve types.
Closes #10220

Solution

Added new spline types and improved existing

---

Changelog

Added

• CubicNurbs rational cubic curve generator, allows setting the knot vector and weights associated with every point
• LinearSpline curve generator, allows generating a linearly interpolated curve segment
• Ability to push additional cubic segments to CubicCurve
• IntoIterator and Extend implementations for CubicCurve

Changed

• Point trait has been implemented for more types: Quat and Vec4.
• CubicCurve::coefficients was moved to CubicSegment::coefficients because the function returns CubicSegment, so it seems logical to be associated with CubicSegment instead. The method is still not public.

Fixed

• CubicBSpline::new was referencing Cardinal spline instead of B-Spline

[JohnTheCoolingFan]

The only thing left is documentation for the new types and methods, I think

[JohnTheCoolingFan]

Ok, the Point trait is no more a blanket implementation and more types implement it, specifically Vec4 and Quat. There are reasons why I didn't implement it on more types:

1. glam's MatX do not implement Div<f32>, only Mut<f32>, which I reported here: impl Div<f32>/Div<f64> for [D]MatX bitshifter/glam-rs#476
2. Color from bevy_color and other color types also do not implement all the math operation traits required. I'm not sure whether implementing them wouldn't produce anything undesirable, so I would like to get more opinions, and implementing this would probably be better as a different PR
3. f64 and types based on that don't interoperate with f32. So unless Point gets a generic argument or associated type specifying the type (f32, f64, potentially even more if it makes sense). Same for integers.

[alice-i-cecile]

Like I said on Discord, I'd like to leave the Color implementations for follow-up :) Doing a final review pass now.

[alice-i-cecile]

I'm happy with this now. Excellent work, and thanks for your patience. I'd like to see more learning materials / examples for this area of the engine, but that can definitely be done in follow-up.