chore: improve input value handling

[pskelin]

<ui5-input> has a very complex logic for handling type=numeric, implemented by keeping _innerValue.

This has two issues:

1. a patch is necessary in preact to render a value in the DOM only when it is different from the old value.
2. this prevents forcing an old value on the input in case an event handler decides not to accept new state

This fix remove the preact patch returning it to default - if a value is set in the tempate, it will be set in the DOM (for native inputs this will always assign a value from the state, even if it is the same)

By removing the _innverValue, apps can automatically set an old value and it will propagate in the DOM.

Example before - an input that accepts only three numbers by setting the old value if more than three numbers arrive

type `123` -> input value is `123`
type `1234` -> input value prop is `123` but input value in dom is `1234`

Example after - when setting an old value, it will be updated in the inner input, so typing 1234 will correctly result in 123 both in .value property and in DOM.

see Input_old_value.html for example code

[ui5-webcomponents-bot]

🧹 Preview deployment cleaned up: https://pr-10935--ui5-webcomponents.netlify.app

[MapTo0]

looks good for inputs

[ilhan007]

• 1 (the test are green)