Bump hatasmota to 0.0.26

[effelle]

Proposed change

Bump hatasmota from 0.0.25 to 0.0.26 which adds some new status sensors.
Also make sure all status sensors are added as hidden entities.

Changes:

• 0.0.26 (https://github.com/emontnemery/hatasmota/releases/tag/0.0.26)

  • Add additional status sensors (#27)
  • emontnemery/hatasmota@0.0.25...0.0.26

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

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.
• 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 @emontnemery, mind taking a look at this pull request as its been labeled with an integration (tasmota) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[MartinHjelmare]

Why is this part of the patch milestone?

[emontnemery]

@MartinHjelmare I added it to the patch milestone to make sure all status sensors are added as hidden entities. It's a bit of a mixed bag though since 0.0.26 also adds some new status sensors.

[MartinHjelmare]

That's a new feature and we don't allow those in patch releases.

[emontnemery]

OK, removed from milestone.
Is it possible to open a PR targetting only the patch release, or should we revert this one and split in two: one to bump hatasmota and one to fix hiding of sensors?

[MartinHjelmare]

Both are possible. If we target the rc branch directly the PR should be labeled with cherry picked label to avoid getting cherry picked again, I think. Please coordinate with the person doing the patch release in this case.

[emontnemery]

OK, replaced by #42643 + #42644