feat(ui): add input event to QInput

[NitroRCr]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Documentation
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes
• No

The PR fulfills these requirements:

• It's submitted to the dev branch (or v[X] branch)
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• It's been tested on a Cordova (iOS, Android) app
• It's been tested on an Electron app
• Any necessary documentation has been added or updated in the docs or explained in the PR's description.

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to start a new feature discussion first and wait for approval before working on it)

Other information:

Due to IME composition detection, model-value of QInput does not update during the IME composition process. However, there are times when we want to handle input during the IME composition process. (referring PR #17476 ) Therefore, input event has been added:

• Emitted during input, even during IME composition.
• No debounce.

The corresponding event was not added on QSelect because the native input event can be directly listened to on QSelect.

Additionally, a bug in select-part-7-text.vue in the playground has been fixed.

[github-actions]

UI Tests Results

    1 files     98 suites   38s ⏱️
1 031 tests 1 031 ✅ 0 💤 0 ❌
1 050 runs  1 050 ✅ 0 💤 0 ❌

Results for commit c744cb6.