Add Garmin Connect integration

[cyberjunky]

Description:

Provides sensors for quite a few values exposed in Garmin Connect.

Implemented async and configflow, dropped yaml cfg for now

Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#11752

Example entry for configuration.yaml (if applicable):

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[cyberjunky]

Looking into flake8 failure.

[cyberjunky]

Need to decide about correct/wanted config name for the resources.
I'm now using the home-assistant's native in the code:

CONF_MONITORED_CONDITIONS

But FitBit uses a local declared:

CONF_MONITORED_RESOURCES = "monitored_resources"

And I believe there is also a:

CONF_RESOURCES

Any suggestion/preferences?

[cyberjunky]

Need to decide about correct/wanted config name for the resources.
I'm now using the home-assistant's native in the code:

CONF_MONITORED_CONDITIONS

Any suggestion/preferences?

Doing a fgrep -R inside the components directory shows that the usage of CONF_MONITORED_CONDITIONS is the highest, so sticking with that one.

[balloob]

We're phasing out the usage of monitored conditions per ADR-003. Please remove that support.

[MartinHjelmare]

Please use the core interfaces in the test to make them more robust.

[paularmstrong]

Just want to poke in and say thanks @cyberjunky for diving into this and @MartinHjelmare for all of your patience and assistance on the code review.

Really looking forward to having this integration for myself!

[cyberjunky]

I see this error in the CI logs pytest for python37:
Is this something I can/need to fix?

import file mismatch:
imported module 'test_config_flow' has this __file__ attribute:
  /__w/1/s/tests/components/garmin_connect/test_config_flow.py
which is not the same as the test file we want to collect:
  /__w/1/s/tests/components/netatmo/test_config_flow.py
HINT: remove __pycache__ / .pyc files and/or use a unique basename for your test file modules

[MartinHjelmare]

The netatmo integration is missing an init module in its test package.

https://github.com/home-assistant/home-assistant/tree/dev/tests/components/netatmo

If you have time, you can open a separate PR and just add an __init__.py module in that directory.

[cyberjunky]

Done #31189

[MartinHjelmare]

Looks good!

[cyberjunky]

I think I have applied all requested changes, I have one thing left; This change let the test_config_flow mock and the check fail again for the already configured test:

        await self.async_set_unique_id(unique_id)
        self._abort_if_unique_id_configured()

        # entries = self._async_current_entries()
        # for entry in entries:
        #     if entry.data[CONF_ID] == unique_id:
        #         return self.async_abort(reason="already_configured")