Add WS API for extended Tasmota device info

[emontnemery]

Proposed change

Add WS API for extended Tasmota device info.
Frontend PR: home-assistant/frontend#7863
Bump hatasmota from 0.1.2 to 0.2.0

Changes:

• 0.2.0 (https://github.com/emontnemery/hatasmota/releases/tag/0.2.0)
  • Add device status #53 @emontnemery

emontnemery/hatasmota@0.1.2...0.2.0

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.

[ctalkington]

hum wonder if we could do this in a way that allows additional device info across all integrations, some kinda method on the entity like get_device_attributes or something and just a single WS endpoint that serves it up and the front-end just loops over it

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.