[Core] Add scalar versions of Vector* min/max/clamp/snap(ped)

[AThousandShips]

Convenience for a number of cases operating on single values

Added a lot of use cases, which I think should justify this addition, it simply saves a lot of code when you use repeated cases, and also reduces risk of copy errors

Optionally bound it to scripting

See also:

• Expose Vector* component-wise and scalar min/max to scripting #80223

If it gets merged first I will expose the mini/minf/maxi/maxf methods as well, and vice-versa

[Mickeon]

Documentation is completely fine and consistent with the existing methods. I just am not sure if having it exposed is strictly necessary.

[AThousandShips]

I'd say these methods are more generally useful than the vector versions, most of the time you want to clamp or snap to the same value, though in GDScript you do have the benefit of being able to do vec.snapped(Vector2.ONE) which you don't have in C++, but vec.snappedf(1.0) is still way cleaner, and especially vec.snappedf(2.0) is way better than vec.snapped(Vector2.ONE * 2.0)

[aaronfranke]

I think this function is a good idea, it seems very common and useful.

[Riteo]

Finally gave a good look at this thing.

All the changes are very simple and they increase readability a lot, great job!

[akien-mga]

Thanks!

[AThousandShips]

Thank you!

[akien-mga]

For the record, this seems to have broken LTO builds for Windows x86_32 with MinGW-GCC. See #92585 for details.