Allow tooltips to show true value

[EAinsley]

Fix #86371

simplescreenrecorder-2024-10-15_16.15.06.mp4

Add a new variable to store the true value. When the range is in the editor, the value_changed signal will emit if the true value changed. When the range is in game, the behavior remains the same.

editorspinslidertooltip.zip

[EAinsley]

Just found it seems I have made some serious performance degradation. I'm not sure what caused this. Convert to draft first.

[EAinsley]

My commit didn't introduce the problem.

I was testing on archlinux with Nvidia GPU, and the editor freezes from time to time. After tracing, I find vkWaitForFences blocks forever.
The issue exists on v4.4.dev.custom_build [af77100], and it's not related to this commit. I will create an issue after I did more tests.

[KoBeWi]

This is editor-only fix, so the changes should be exclusive to EditorSpinSlider. You can add "true value" to EditorSpinSlider only; the downside is that shared->val == p_val condition will not take it into account, but I think it won't cause any serious problems.

[KoBeWi]

So there is a problem actually.
The inputted value ignores step. If you export a property with @export_range(0, 100, 0.1), you can still put a higher precision value than the step. It will be displayed in the tooltip and get stored in the scene file. Though maybe the fix is simply removing the get_value() override.