Climate validate temperature(s) out of range

[gjohansson-ST]

Proposed change

Previously the climate entity min and max temperature values was used only for frontend displaying correctly but no validation against what the user could set (if not managed by the integrations themselves).
This PR adds a validation to so if the temperature(s) sent in are less than min or more than max it will raise a validation error and not pass to the integration.

Dev docs PR: home-assistant/developers.home-assistant#2259

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
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format 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 (climate) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of climate can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign climate Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[frenck]

I like the goal of this PR, @gjohansson-ST 👍 It will help finding bugs and other unexpected behaviors.

[gjohansson-ST]

Test failure is unrelated. Seems there is quite some flaky tests

[frenck]

Thanks, @gjohansson-ST 👍

../Frenck

[gjohansson-ST]

Test failure (spc) isn't related to this PR so will merge it in now.

[MartinHjelmare]

We have this helper:

core/tests/common.py

Line 1737 in 6baee60

def setup_test_component_platform(

[elupus]

May need to allow opt-out of this feature. See #128118