Fix Airly if more than one config entry

[bieniu]

Breaking Change:

None

Description:

My stupid mistake cause issue with few instances of the integration. This PR fix that.

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.

[MartinHjelmare]

Is there a github issue connected? Please describe what problem we're addressing and why this fixes it.

[bieniu]

@MartinHjelmare If two instances of Airly integration are added, only the second one will be properly initialized at HA startup. First AirlyData object of config_entry will be removed from hass.data[DOMAIN][DATA_CLIENT] due this. This PR moves

hass.data[DOMAIN] = {}
hass.data[DOMAIN][DATA_CLIENT] = {}

to the right place: async_setup function.

This issue hasn't reported via GitHub. Someone from polish Home Assistant group on Facebook told me about that.

[MartinHjelmare]

Good! Thanks!

[MartinHjelmare]

Failed tests are unrelated and have already been fixed on dev branch.