fix: Update range component to not trigger changes immediately after typing (close #643)

[maldoinc]

Please check if the PR fulfills these requirements

• It's submitted to right branch according to our branching model
• It's right issue type on title
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes/features)
• Docs have been added/updated (for bug fixes/features)
• It does not introduce a breaking change or has description for the breaking change

Description

Hi all, in this PR I propose a change to the way the Range component handles user input. Currently, input will be processed immediately and in case it is smaller than a certain minimal value it will be replaced with the minimum value making it impossible to type widths such as "150" due to it because as soon as you select the text and type "1", that value will be replaced with "32".

The PR handles input differently by allowing the user to have a grace period of 350ms and only after that time passes is the input processed. This also addresses #643, which is the same problem experienced by another user of the library.

Looking forward to your input.

[lja1018]

@maldoinc
Thank you for your contribution.
If you apply for the review, I'll merge.

[philipeatela]

Thank you for this!

[lja1018]

@maldoinc
Merge this PR into the master.
It will be included in the next version (probably 3.15.3).