Improve range property hints for various collision shapes

[Xrayez]

Closes #36419.
Helps #19242.

The current limits seem to be unreasonably high for shapes, when you drag a slider it's often too difficult to set a value which wouldn't jump from minimal size/length to a size which covers the whole viewport (meaning it only takes 4 range steps to exceed the shape's size beyond visible screen in most cases). Fine-tuning helps but doing this every time is tiresome.

The maximum ranges:

• for 2D: 1024 pixels or greater (was 16384);
• for 3D: 128 units or greater (exact ranges as in CSG nodes) (was 4096).

The maximum values for 2D and 3D are picked by an "equal" number of mouse-wheel scrolls it takes to fully enclose a shape for it to become visible inside the editor viewport (in most cases).

Slow stepping for 2D is taken into account: #866, so I didn't change the current step (0.5 pixels).

[Xrayez]

Again, merge conflicts which I'm not willing to resolve at the moment given this enhancement is not critical, so might be salvageable, but this likely needs more discussion as in #19242.

[Xrayez]

For 3D shapes, I've just made it consistent with CSG nodes now, yet those don't allow "or_greater", which can be added too. For 2D, this is still the same as described in OP.

[akien-mga]

Superseded by #59550.