[MIRROR] Makes the restricted number input user friendlier

[Steals-The-PRs]

Mirrored on Nova: NovaSector/NovaSector#1037
Original PR: tgstation/tgstation#81495

About The Pull Request

The modal number input is extremely user unfriendly in it's current state whenever used for negative and decimal numbers See #81457 for details. The code might not be the best and if someone has suggestions to optimize it, I'm all open for it, but it takes into aspect a lot of edge cases to make the input as user friendly as possible. I've also heard form some other code bases that they have issues with the tgui_input_number proc.

The RestrictedNumber will get a new event to listen to though:

onBlur={(_, value) => onBlur(value)}

This will run the number through the previous, hard sanitation and ensures that we always submit an allowed number and not a string value as we are using it shortly during input for the pure - input. (Especially important for the "Submit" button. Enter always handles it that way). During testing, all the tested numbers were handled properly, I could not see any issues on the inputs. We still keep some in Field replacement, but it's for a limited range where we can have the field handle numbers smart:

min <= 1 && max >= 0: Within that range, the field updates the value to the restrains on input. In all other cases only onBlur.

Testcase table:

Test case	Field Limit	Input	InField	OnEnter	OnSubmit	OnBlur
Float (smart)	1-20	0	1	1	1	1
		1.1	1.1	1.1	1.1	1.1
		20.1	20	20	20	20
		-		1	1	1
		.	1.	1.	1.	1.
		5	5	5	5	5
Float	2-20	0	0	2	2	2
		2.1	2.1	2.1	2.1	2.1
		5	5	5	5	5
		20.1	20.1	20	20	20
		-		2	2	2
		.	2.	2.	2.	2.
Float with decimal limit	20.2-200.2	0	0	20.2	20.2	20.2
		20.	20.	20.2	20.2	20.2
		50	50	50	50	50
		200.3	200.3	200.2	200.2	200.2
		-		20.2	20.2	20.2
		.	20.	20.2	20.2	20.2
Float with decimal limit (smart)	0-20.2	0	0	0	0	0
		20.	20.	20.	20.	20.
		5	5	5	5	5
		20.3	20.2	20.2	20.2	20.2
		-		0	0	0
		.	0.	0.	0.	0.
Negative Float (smart)	-10-20	-10.2	-10	-10	-10	-10
		20.	20.	20.	20.	20.
		20.1	20	20	20	20
		0	0	0	0	0
		-	-	-10	-10	-10
		.	-10	-10	-10	-10
		-.	-10.	-10.	-10.	-10.
		-10-	10	10	10	10
		10-	-10	-10	-10	-10
Negative Float with decimal limit	-10.2--20.2	-10.1	-10.1	-10.2	-10.2	-10.2
		-20.	-20.	-20.	-20.	-20.
		-20.3	-20.3	-20.2	-20.2	-20.2
		0	0	-10.2	-10.2	-10.2
		-	-	-20.2	-20.2	-20.2
		.	-20.	-20.	-20.	-20.
		-.	-20.	-20.	-20.	-20.
		-10.2-	10.2	-10.2	-10.2	-10.2
		10.2-	-10.2	-10.2	-10.2	-10.2
Int (smart)	1-20	0	1	1	1	1
		1.	1	1	1	1
		21	20	20	20	20
		5	5	5	5	5
		-		1	1	1
		.		1	1	1
Int	20-200	19	19	20	20	20
		201	201	200	200	200
		50	50	50	50	50
		-		20	20	20
		.		20	20	20
Negative Int (smart)	-10-20	-11	-10	-10	-10	-10
		0	0	0	0	0
		21	20	20	20	20
		-	-	-10	-10	-10
		.		-10	-10	-10
		-.	-	-10	-10	-10
		-10-	10	10	10	10
		10-	-10	-10	-10	-10
Negative Int	-200---20	-201	-201	-200	-200	-200
		-19	-19	-20	-20	-20
		-50	-50	-50	-50	-50
		-	-	-200	-200	-200
		.		-200	-200	-200
		-.	-	-200	-200	-200
		-20-	20	-20	-20	-20
		20-	-20	-20	-20	-20

Why It's Good For The Game

Even though not used often on TG code, the modal inputs are used on other code bases and inputting numbers has been a hell if it was anything other than a positive integer. This PR aims to make the handling as user friendly as possible, even if it's a lot more edge case checking than the very simple code beforehand.

Changelog

fixes #81457
🆑 Kashargul
qol: makes the tgui_input_number user friendly for negative and decimal inputs
code: the onBlur={(_, value) => onBlur(value)} event should now be used on all uses of RestrictedInput to ensure that the number is fully sanitized whenever the user leaves the field or submits it through a button
/:cl: