fix: handle selectionRange on different input types

[ph-fritsche]

What:

Refactored how selection is applied to input elements.
Fixed how selection is handled for input elements (type="number") that don't support selection ranges.
Used fixed selection handling for {selectall}.

Why:

Closes #501 .
Required for fixing #583 .

Checklist:

• N/A Documentation
• Tests
• Ready to be merged

[codecov]

Codecov Report

Merging #619 (fa9f52a) into master (7ff9a9a) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #619   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           47        46    -1     
  Lines          874       881    +7     
  Branches       324       330    +6     
=========================================
+ Hits           874       881    +7     

Impacted Files	Coverage Δ
src/utils/edit/calculateNewValue.ts	100.00% <ø> (ø)
src/keyboard/plugins/arrow.ts	100.00% <100.00%> (ø)
src/keyboard/plugins/control.ts	100.00% <100.00%> (ø)
src/keyboard/plugins/index.ts	100.00% <100.00%> (ø)
src/keyboard/shared/fireInputEventIfNeeded.ts	100.00% <100.00%> (ø)
src/paste.ts	100.00% <100.00%> (ø)
src/type/typeImplementation.ts	100.00% <100.00%> (ø)
src/utils/edit/hasUnreliableEmptyValue.ts	100.00% <100.00%> (ø)
src/utils/edit/selectionRange.ts	100.00% <100.00%> (ø)
... and 1 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7ff9a9a...fa9f52a. Read the comment docs.

[github-actions]

🎉 This PR is included in version 13.0.11 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀