Add config flow to Brottsplatskartan

[gjohansson-ST]

Breaking change

The Brottsplatskartan integration has been migrated to configuration via the UI. Configuring via YAML configuration has now been deprecated and will be removed in a future Home Assistant release.

Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.

Proposed change

Implement config flow for brottsplatskartan

Type of change

Implementation of config flow

• 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

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Add config flow to brottsplatskartan home-assistant.io#22475

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.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

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

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[github-actions]

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.

[gjohansson-ST]

Not stale. Awaiting review.

[luar123]

LGTM

[github-actions]

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.

[gjohansson-ST]

Not stale

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[gjohansson-ST]

Coverage 100%

---------- coverage: platform linux, python 3.10.10-final-0 ----------
Name                                                        Stmts   Miss  Cover   Missing
-----------------------------------------------------------------------------------------
homeassistant/components/brottsplatskartan/__init__.py          9      0   100%
homeassistant/components/brottsplatskartan/config_flow.py      39      0   100%
homeassistant/components/brottsplatskartan/const.py             9      0   100%
-----------------------------------------------------------------------------------------
TOTAL                                                          57      0   100%

[epenet]

A few last comments, and a question.: how were multiple areas meant to work previously, and why now restrict to a single area?

[epenet]

As per comments above.

[gjohansson-ST]

A few last comments, and a question.: how were multiple areas meant to work previously, and why now restrict to a single area?

It wasn't. Before and now you can only configure one area.
No clue why they set it as a list whomever created it.

[epenet]

LGTM 👍

[frenck]

Removed the breaking change, as this is raising an issue in the repair center.