Add configuration flow for Buienradar integration

[RobBie1221]

Breaking change

This PR will deprecate yaml support for Buienradar integration and add UI configuration. The yaml configuration will be imported once. When users have a weather and sensor setup for same coordinates, they will be merged into one ConfigEntry. Only one camera configuration will be imported.

Following things are changed:

• The forecast key of the weather platform is deprecated, forecast data is fetched in the same API call and to be in line with ADR-0003, all available data is exposed.
• Weather, sensor and camera domain are setup in one ConfigEntry. For new entries, sensor and camera entities are disabled by default.
• Dimension for camera images is fixed to 700 pixels

Proposed change

This PR implements a basic configuration flow for the Buienradar integration. The integration currently includes the weather, camera and sensor platform. With the flow in this PR, you can setup all three in one configuration flow. The user can choose whether to include the radar image as camera, because this is fetched as image with a separate API call. The user is able to configure multiple instances as long as the lattitude/longitude is unique.

Furthermore, a "Name" attribute is now mandatory, which is used to create entities. In the Integrations page, the Buienradar card will show up with this configured name.

Setting options will be addressed in a later PR.

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)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Update buienradar.markdown for config flow home-assistant.io#14000

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
• 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.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

[RobBie1221]

Work in progress, config flow is fully implemented. Todo is change the current tests to work again and add tests for the configuration flow

[RobBie1221]

This is basically done. See limitations in description, but first I'd like to get this approved. Also the weather writes to hass.data[buienradar_condition] which I think should be refactored to hass.data[DOMAIN]. The unload will most likely leave the data updater intact, which is not really nice when removing the integration without restart. I'll address this as well in a later PR.

[RobBie1221]

@mjj4791 @ties Mind taking a look at this as well?

[OnFreund]

This looks good to me, but keep in mind someone with write access will have to approve as well.

[stale]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

[RobBie1221]

Waiting review, not stale

[Kars-de-Jong]

Some minor comments about comments ;-)

[ties]

I think this still looks relevant functionally. @RobBie1221?

[RobBie1221]

Yes, just waiting for a review.

[FeikoJoosten]

@RobBie1221 would it be possible to add the proposed changes from my PR to this PR?

I don't mind waiting till this PR is merged to do it myself, but since the changes are small I figured I might ask you for it.

[frenck]

Tested again, still works great. Thanks, @RobBie1221 👍

Going to ask for a second look/opinion from a fellow reviewer, but I think it's great 🎉

[RobBie1221]

I think I got them all :-)

[MartinHjelmare]

Great!

[MartinHjelmare]

Sorry, I noticed some things that we should address in the tests. It seems there's no I/O directly during config entry setup but the platforms will eventually do I/O so it's safest to patch that regardless.

[RobBie1221]

I'll address these in a follow-up PR