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

[AThousandShips]

Added for convenience, which was mentioned in the PR changing the behavior of the generic min/max

If the naming is considered confusing we can use component_max/min just to make it more clear (though more verbose)

Will open a godot-cpp equivalent as well
Done: godotengine/godot-cpp#1197

• Closes: Expose Vector* component-wise min/max to scripting godot-proposals#7439

[MewPurPur]

Regarding the resolved comment above, shouldn't documentation examples, on the contrary, avoid static typing? So no mini() and minf() for example?

[AThousandShips]

Here the typing is static because of the vector types, no, and the specific versions have better performance so would recommend using them whenever reasonable? But can switch back if desired

[AThousandShips]

Added note to the documentation in line with #84656

[raulsntos]

Unfortunately the Min/Max ones don't fit in the integer vector versions because they already have Min/Max as constants

Luckily those members have been added in 4.2 (#81819) which is still unreleased so we have a chance to rename them. I would name them MinValue and MaxValue to match the int names. Then we can use the Min and Max names for the methods which seems consistent with the methods in Mathf.

[AThousandShips]

Great! Was considering that, will make the changes here and see what ends up happening

[AThousandShips]

Resolved it for the CI here, but would be maybe good to get a dedicated one for C# done for 4.2 anyway

I'll go ahead and make one

[akien-mga]

Thanks!

[AThousandShips]

Thank you!