Fix min and max macro not enforcing limits when data flows

[mTvare6]

Fixes https://discord.com/channels/731730685944922173/731738914812854303/1351538875390099507.

[Keavon]

Requires hard/soft range rework discussed in Discord.

[mTvare6]

@Keavon I've changed them into hard_min and min(considering it to be the default). Do let me know if it should instead be called soft_min.

[Keavon]

@TrueDoctor can we avoid needing to include these trait bounds for T here?

[TrueDoctor]

Yes I described the solution when this was discussed originally, I still might have the partial code for that somewhere. These bounds should basically automatically be added by the macro

[TrueDoctor]

But we can also add that as a todo and implement that later if there are enough users that not having it becomes annoying

[TrueDoctor]

Why do we have hard min and max but no hard/ soft ranges? And I'm not a fan of how the attributes are stored after parsing. Please choose a data representation which more closely aligns with what is a valid state. ( e.g. it shouldn't be possible to specify both hard and soft min and there should be a good error message in that case

[Keavon]

Why do we have hard min and max but no hard/ soft ranges?

Range is always soft, it refers to how far left and right the draggable range slider goes. Specifying a range (to get the dragging slider kind of number input) and a hard min/max would be the expected way to set a range slider and prevent the user from typing values beyond the intended allowable bounds.

it shouldn't be possible to specify both hard and soft min and there should be a good error message in that case

If the soft min is larger than the hard min, that's allowed. But you're right that an error should be shown if they are equal (if so, soft should be removed) or reversed (this would indicate a mistake).