fix(input): only set native input value if different

[sean-perkins]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally and any changes were pushed
• Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

setSelectionRange isn't supported on all input types and will error when developers use ion-input with a type other than: text, url, search, tel, or password.

Issue Number: #24753

What is the new behavior?

Removes the logic requiring the usage of setSelectionRange and rather only sets the native input value if not composing (using an IME) and if the value is different than the current value).

Fixes error resulting in:

Failed to execute 'setSelectionRange' on 'HTMLInputElement': The input element's type ('number') does not support selection.

Does this introduce a breaking change?

• Yes
• No

Other information

[averyjohnston]

Might want to update the PR name and description, since you're doing something entirely different now. Otherwise, this LGTM; I tried it on Windows Chrome, plus iOS 14 and 15, and couldn't poke any holes besides the behavior you noted here.

[sean-perkins]

Good call, I've updated both. Not in love with the PR title, but unsure how to best describe it.