Add Support for VeSync Devices - Outlets and Switches

[webdjoe]

Breaking Change:

Vesync integration is now a complete component, cannot be setup by individual platforms (i.e. switch). In addition to adding the Vesync component through configuration.yaml, it can also be added through the integration menu in the configuration UI.

The Vesync component no longer supports this syntax in configuration.yaml:

switch
  - platform: vesync
    username: EMAIL
    password: PASSWORD

If using It must be set up using vesync as a component:

vesync:
  username: EMAIL
  password: PASSWORD

Description:

Convert VeSync switch platform to a full component. Can be configured through the integration menu in the configuration front-end or through configuration.yaml. Add support for the European 10 Amp smart outlet (ESW10-EU), US 15 Amp rectangular outlet (ESW15-USA), US 10 Amp round outlet (ESW10-USA), two plug outdoor outlet (ESO15-TB) and in wall switch (ESWL01).

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

Example entry for configuration.yaml (if applicable):

vesync:
  username: EMAIL
  password: PASSWORD

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.

[frenck]

Tests for the config flow is required.

[webdjoe]

Do I just have to test the config flow or the whole integration?

[frenck]

Tests for the config flow (if used) is the minimal requirement.

[MartinHjelmare]

Great!

[MartinHjelmare]

Please add to the breaking change paragraph what the user needs to do to cope with the breaking change.

[webdjoe]

Thanks for your patience in guiding me through this, I have a much better grip on the HA architecture!

[MartinHjelmare]

Thanks for the feedback!

PR can be merged when build passes.