WIP: Locale Inputs, Resolving broken embroiderer dependencies, Unfocus Formatting

[ErvinSabic]

This seeks to solve a few issues:

#468
#483

Dependency issue mentioned by Windvis here - #540 (comment)

Will mark as ready when I believe it can be submitted for review.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4614ab0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[simonihmig]

Hey @ErvinSabic, thanks for working on this! Just kicked off CI. Tests including Embroider are passing! 🎉 But some type errors, fyi

[ErvinSabic]

Yep! Still working on it. o7

[ErvinSabic]

@simonihmig I encourage you to give this a try locally. I'm going to be writing more tests for it and I want to try it on a mobile device as well to see what happens with the caret positioning.

It should work for:
Whole numbers,
Decimals,
Currencies,
Percentages,
Units. (Mostly)

Does not support:
Scientific Notation
Compact Notation

It is worth noting that there are edge cases with the way Intl.NumberFormat may handle some things. For example, in a Saudi Arabian Locale if you enter "2" in a input that is setup for units, and the units being liters, that locale actually has a specific word that communicates "2 liters". Just based on my testing. I imagine it's much like how an American might call "12 eggs" a "dozen eggs". Though I'm not a linguist and I don't speak arabic. I'm stopping here because if I keep chasing edge cases this will never get done and in its current form supports the majority of use cases one might expect out of a component like this.