Improve dragging float number fields in the inspector

[vitorbalbio]

Describe the project you are working on:
Space Tactical RPG https://twitter.com/ZeroPointGame

Describe the problem or limitation you are having in your project:
This proposal is part of a much more complete UI/UX overhaul and should be considered with this view about Godot Editor problems and possible solutions: #1503

Dragging Float Number Input Fields

When dragging a number input field in inspector the values seems normalized by type. What it means is that if a field has float values they are always normalized in -1 to 1 and Integer in -1000 to 1000 (Don't know the right values but this is the amplitude of a mouse movement approximately). There's a modifier to allow to decrease the rate of change and it's useful to integers but for float values with large numbers like used in Transform Inspector it is useless. Is currently impracticable to handle float fields that use values > 1 without a tendinitis.

Describe the feature / enhancement and how it helps to overcome the problem or limitation:
Describe how your proposal will work, with code, pseudocode, mockups, and/or diagrams:

Normalize the float values the same high numbers it's done with Integers but add a proporcional mouse movement in a way that slow mouse movements will change by 0.1, mid will change by 1.0 and fast will change to 10. That way you can keep the same amplitude of values you have in int number fields and keep the resolution if the user want to change small values. This can also be applied to int unifying the behavior but with another scale 1/10/100 e.g

Keeping the SHIFT modifier also could force the lower change rate independent of the mouse velocity. Also if something is normalized only in small values like 0~1 it would use the slider component anyway. It would fix manipulation in all Transform inspector parameters and exported float fields.

If this enhancement will not be used often, can it be worked around with a few lines of script?:
Will be used often

Is there a reason why this should be core and not an add-on in the asset library?:
It's a core editor feature.

[jordanlis]

also, when the mouse button is pressed, we should display left and right arrows to help the discoverability of this feature