Rename RayShape to SeparationRayShape

[Xrayez]

Describe the project you are working on:
Godot Engine

Describe the problem or limitation you are having in your project:
There are certain confusion over the real intention and usage of the classes.

Describe the feature / enhancement and how it helps to overcome the problem or limitation:
Renaming the classes to reflect the intended usage shall resolve the confusion. In this case, explicit is better than implicit.

Describe how your proposal will work, with code, pseudocode, mockups, and/or diagrams:
Renaming is already suggested by official article as in:
https://godotengine.org/article/godot-31-will-get-many-improvements-kinematicbody

RayCast shapes separate the body in the direction they are pointed to, and will always return a collision normal along their ray, instead of the one provided by the floor (because, again, their goal is to separate). Yes, the name is confusing, maybe they should be renamed to SeparationRayShape in Godot 4.0 :)

Alternatively, it may be worth implementing #333 and just rename this to SeparationShape which would accept any existing shape Shape (or just allow any shape to act as separation shape for that matter). Marginally related proposal for ShapeCast node: #710.

If this enhancement will not be used often, can it be worked around with a few lines of script?:
Possible to create a script wrapper over the existing class.

Is there a reason why this should be core and not an add-on in the asset library?:
People should not get confused between ray casting and ray shapes used for physics separation and should be advertised by the engine devs instead.

[Jummit]

godotengine/godot#16863

[Calinou]

Tracking renames is probably better done in the issue @Jummit linked. You generally don't need to write a formal proposal for this 🙂

[Xrayez]

@Calinou do you think same can be said for #652?

It's just that it's likely to attract controversial discussions and whatnot, which worth an entire proposal. 🙂

[Xrayez]

This is probably better to be tracked by godotengine/godot#16863 as suggested. I've done some refactoring to make the transition more consistent: godotengine/godot#39209. I feel like the renaming itself asks for more underlying renamings, and I don't feel like doing this myself (honestly). 🙂

[Zylann]

I'm actually confused by this new name. Why SeparationRayShape? Where does the "separation" comes from? In the context of a game engine I always thought "ray" was enough to describe a point with a direction, max distance and one possible hit. If some newcomers get to use such a shape and not understand that, it sounds like a documentation issue. IMO, what may be confusing more than the name, is the fact considering "ray" to be a "shape", it's a bit of a stretch. If the confusion comes from the single-hit, then it could internally be a line-cast with results ordered by distance, if more than one result is wanted, dunno.

[Xrayez]

There's a PR godotengine/godot#51896, so I assume this change is desired, so reopened.