Add step validation to input_number and number selectors

[jbouwh]

Proposed change

Add step validation to number selectors to only call the setValue API if there is a valid step value selected.

The entity row UI number control has a red border when the step is invalid (autoValidate).
Enabled autoValidate on the state card to ensure the same behavior.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

The MQTT number config example below can help to test the change (turn debug logging on for mqtt).

mqtt:
  - number:
      command_topic: test/number
      min: -18
      max: 40
      name: Test number
      mode: box
      step: 5

Additional information

• This PR fixes or closes issue: fixes The "step" variable does not work for number in the box mode #20168
• This PR is related to issue or discussion: The "step" variable does not work for mqtt number in the box mode core#113956
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

[ildar170975]

Assume an input_number helper is defined with step: 1 (i.e. w/o fractions).
Will it be still possible to input values like 123.123 ?

[jbouwh]

Assume an input_number helper is defined with step: 1 (i.e. w/o fractions). Will it be still possible to input values like 123.123 ?

I think so, but I'll do some additional testing to conform this. The test size of the entity is used BTW, not 1.

[jbouwh]

Converting to draft, as this works not well yet if not the native unit is set in the UI.

[jbouwh]

This PR is not ready, but the approach is not good., so closing this for now,

[il77781]

@jbouwh, understood you. Well, it's a pity...