Add myuplink diagnostics download

[astrandb]

Breaking change

Proposed change

Add module for diagnostics download. All relevant data from the myUplink API is captured and dumped.

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:Add myuplink diagnostics to ha_platforms home-assistant.io#31386

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 Ruff (ruff format 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 @pajzo, mind taking a look at this pull request as it has been labeled with an integration (myuplink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of myuplink 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 myuplink Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[elupus]

I think the system id should be redacted too. I think the info may contain house address, at least the old nibeuplink data could do that.

We also need to see an example of the diagnostic info to see if more things should be redacted. Preferably as some test case.

[astrandb]

I cannot find any sensitive data in the output from the API, system id and device id are UUID-style strings. Please have a look at the file from my unit. (I dont know any emmy ;-) )

config_entry-myuplink-8016ca074b552af9dca334f133abb752 (9).json

[elupus]

Serial number, and preferably device/system id. But it looks hard to filter. At least redact serial number.

[astrandb]

Hiding serialNumber. Keeping the id:s for the moment. After all, the output file is private to the end-user unless he/she publishes it somewhere.

[MartinHjelmare]

Please add tests. Look at other integrations for examples.

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[astrandb]

@MartinHjelmare

Please add tests. Look at other integrations for examples.

It took a while to make it work. I couldn't find a good example that just worked. The trick was to bypass all OAuth stuff in the optimal place. I think it became pretty clean in the end.

[MartinHjelmare]

Thanks!

[MartinHjelmare]

Normally this should be a separate PR. But since it's small and just tests it's ok this time.

[astrandb]

Thank you @MartinHjelmare for your thorough review and all constructive suggestions.