Add coordinator to QNAP

[disforw]

Breaking change

Proposed change

Moving QNAP integration to coordinator in prep for config_flow

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.

[disforw]

@dgomes would you mind formatting me here? I’m just going to power through this quickly.

[dgomes]

Working with the web interface alone without testing it properly will not get this PR through :(

[epenet]

Like @dgomes said, you should really setup a dev environment... it's not complicated and it will make it easier no only for the reviewers but also for yourself.

[disforw]

I already began working on a brand new dev environment for this, I now see it’s necessary.
Thank you so much for this work, it was extremely helpful!

[disforw]

Ok I think this one is ready

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

[epenet]

One last small thing, regarding type hints.

Can you please also explicitely confirm that the code has been tested against a real QNAP server?

[disforw]

Tested on QNAP server, working perfectly!

[epenet]

LGTM 👍
@dgomes / @starkillerOG anything to add?

[starkillerOG]

Looks good to me!
One small comment related to the config flow PR.

[dgomes]

Tested on TS-251+