Implement track/untracked power group

[bramstroker]

• Implement options flow
• Add more tests, especially the resolution of tracked entities
• Add documentation
• Implement and test utility-meter creation
• For auto entities check if we can use energy individual device configuration
• How to deal with newly added entities or removed entities, can we detect that and reload config entry, or do we need to wait for restart?

[coveralls]

Pull Request Test Coverage Report for Build 12468286870

Details

• 195 of 195 (100.0%) changed or added relevant lines in 11 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 12453475413:	0.0%
Covered Lines:	4865
Relevant Lines:	4865

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 12455270746

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 48 of 56 (85.71%) changed or added relevant lines in 5 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.2%) to 99.833%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
custom_components/powercalc/sensors/group/tracked_untracked.py	32	40	80.0%

Totals
Change from base Build 12452615844:	-0.2%
Covered Lines:	4775
Relevant Lines:	4783

---

💛 - Coveralls