[Editor] Add support for displaying unsigned integers in the inspector

[AThousandShips]

Added these hints to shader uniforms, which is what inspired this improvement

Also made improvements to handling of vector inspector

Still in progress with some details to work out, but basically ready, works well with the specific use case, limited at the moment but useful for the specific use of handling shaders, where editing unsigned values is very difficult from the editor

Considering it a feature, but it technically covers a broken or missing editor feature, I think it speaks for itself in this format, but can open a proposal if desired, but I don't think there's anything more to discuss except implementation details

It's of very limited use for int but for PackedInt32Array and Vector2/3/4i it's very potent

See for background:

• [Rendering] Add hints to some uniform PropertyInfos #89488 (comment)
• shader uniform uint allows negative numbers in inspector panel #89436

---

• Fixes: Editor interpreting unsigned uvec shader uniform parameters as signed  #92064

[RedMser]

Suggested change

Additionally, other keywords can be included: [code]"exp"[/code] for exponential range editing, [code]"radians_as_degrees"[/code] for editing radian angles in degrees (the range values are also in degrees), [code]"degrees"[/code] to hint at an angle and [code]"hide_slider"[/code] to hide the slider, and [code]"display_unsigned"[/code] to allow signed integers to be displayed as unsigned (this is especially useful with [PackedInt32Array]).

Additionally, other keywords can be included: [code]"exp"[/code] for exponential range editing, [code]"radians_as_degrees"[/code] for editing radian angles in degrees (the range values are also in degrees), [code]"degrees"[/code] to hint at an angle, [code]"hide_slider"[/code] to hide the slider, and [code]"display_unsigned"[/code] to allow signed integers to be displayed as unsigned (this is especially useful with [PackedInt32Array]).

"and" appears twice.

[dsnopek]

I wonder if we should go beyond just display_unsigned (which is only about display) to something more like treat_as_unsigned or similar name (which is more about how to interpret the data)?

There's a couple of places in Godot's API where we treat the value of an integer as unsigned, but we don't have a way to formally mark it as such. This has come up in the context of GDExtension a number of times. We've decided to assume that bitfields are unsigned, which covers many of these cases. But having a property hint like this would help with any remaining ones.

cc @Bromeon

[AThousandShips]

That's a good point, would be interested in looking at it, could name it that way here and leave things open for future expansion