Add tests for Sensibo

[gjohansson-ST]

Proposed change

Add tests to Sensibo.
The remaining tests to be added in separate PR following this.

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)
• 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.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[probot-home-assistant]

Hey there @andrey-git, mind taking a look at this pull request as it has been labeled with an integration (sensibo) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[gjohansson-ST]

test_climate_temperature_is_none needs to be rewritten once #71149 is merged

[gjohansson-ST]

Should be good to go I hope

[MartinHjelmare]

We normally put data like this in a json file in a fixtures directory for the tests of the integration. Then load the data in a pytest fixture and return it as needed.

[gjohansson-ST]

Alright. I do that in a new PR before I add the remaining tests.

[gjohansson-ST]

Rethinking: This is a dataclass coming from the upstream package where "raw" is just a minor subset to have for diagnostics.
Not sure if you mean to get the whole dataclass into a json file (seems not ideal) or just the section of "raw"?

[MartinHjelmare]

How you compose the fixture data into files is up to you and how the library response is built.