Split out gpslogger into a separate component and platform

[rohankapoorcom]

Description:

Splits the gpslogger device tracker to be a component in addition to the device_tracker platform. This is required to migrate it over to use the webhook component.

Breaking Change: The gpslogger device_tracker platform no longer takes any configuration. The configuration needs to be applied to the component gpslogger instead. The platform will be automatically loaded with the component and should not be specified in configuration.yaml.

Related issue (if applicable): fixes #

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

Example entry for configuration.yaml (if applicable):

gpslogger:

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.

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:

• New dependencies have been added to the REQUIREMENTS variable (example).
• New dependencies are only imported inside functions that use them (example).
• New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
• New files were added to .coveragerc.

If the code does not interact with devices:

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

[MartinHjelmare]

Looks good!

[MartinHjelmare]

We should update coveragerc too. What's the coverage? Can we remove the device tracker platform or should we add the component?

[rohankapoorcom]

The device tracker platform is currently in .coveragerc. The component is at 83.33%

I can add a couple more component tests and I think we can remove the device tracker platform from .coveragerc.

[MartinHjelmare]

Nice!

[MartinHjelmare]

Can be merged when build passes.

[rohankapoorcom]

Build seems to have failed due to unrelated things, will close/reopen to trigger another.

[MartinHjelmare]

If it's a known flaky test we can just ignore it. But let's see what this build has to offer.

[rohankapoorcom]

Looks like the build succeeded this time. We have 100% coverage on both the component and the platform.