Fix tplink overloading power strips

[bdraco]

replaces #103668 since I can't reopen that one as I forced pushed while trying to get the CI working from open/close

Breaking change

To prevent overloading the power strips, the energy data is only polled every 60 seconds. If you need to poll the data faster, please use an automation that calls the homeassistant.update_entity service.

Proposed change

In #87399 we reduced the polling interval to 5s, and this works great for most devices. However power strips do plugs * N + 1 updates which causes them to get overloaded.

• Split the child power sensors into their own coordinators to reduce the update interval of the power data to prevent overloading the device

Turning on individual sockets is now reliable and doesn't fail ~20% of the time anymore. Also its now possible for the kasa app to be open when setting up the device without it failing.

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

To help with the load of incoming pull requests:

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

[home-assistant]

Hey there @rytilahti, @TheGardenMonkey, mind taking a look at this pull request as it has been labeled with an integration (tplink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tplink 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 tplink Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[bdraco]

I just realized that since I've been running this my database average size has dropped 50mib over 10 days as most of the data was useless churn generated by the voltage and wattage sensors fluxing at 0.00.....

[bdraco]

Thanks. leaving as a draft and will merge later after we fix #103150 since issues are building up there and it likely need to be backported (and it will conflict here)

[bdraco]

Going to merge this now since I keep forgetting to merge it into my integration branch while testing #105143 and I was thinking we had regressed the power strips again