Ensure numeric sensors have a valid value

[epenet]

Proposed change

DO NOT MERGE BEFORE 2023.4.0dev
As follow-up to #85513 and #85863, we can now validate numeric sensors

Type of change

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

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• 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

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (sensor) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of sensor can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign sensor Removes the current integration label and assignees on the issue, add the integration domain after the command.

[epenet]

cc @mib1185 / @flabbamann
I am not sure how to fix the fritzbox tests for this.
https://github.com/home-assistant/core/actions/runs/3885198937/jobs/6629601875

[mib1185]

@epenet the fritzbox tests are fixed 😉

[epenet]

Since #85863 was merged, I have moved the test fixes to separate PRs

Stale

[epenet]

2023.4.0dev is out
I think this can be reviewed again now.

[epenet]

Rebased to ensure CI still passes

[epenet]

As discussed with @emontnemery and @frenck, marking this as draft until beta is cut, so we have a dev cycle with nightlies to act on

[epenet]

2023.5.0dev is out
I think this can be reviewed again now.