Convert somfy to use DataUpdateCoordinator

[bdraco]

Proposed change

Convert somfy to use DataUpdateCoordinator

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

Example entry for configuration.yaml:

# Example configuration.yaml

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

[bdraco]

I have a lot of RTS devices so no more jumps into the executor only to hit the throttle since the coordinator takes care of the updates.

I read the profile wrong. It wasn't this one that was causing all the executor jobs. Well one more integration converted 👍

[tetienne]

For later, it would be nice to increase the poll interval (to the refresh token date) when all the devices are in assumed state.

[bdraco]

For later, it would be nice to increase the poll interval (to the refresh token date) when all the devices are in assumed state.

Will do in the follow up.

We can probably poll hourly?? in this case.

[tetienne]

If it’s less than the refresh token interval, yes.

[bdraco]

For later, it would be nice to increase the poll interval (to the refresh token date) when all the devices are in assumed state.

Will do in the follow up.

We can probably poll hourly?? in this case.

done here #42462