Add config flow to fritzbox_callmonitor

[springstan]

Breaking change

Proposed change

Adds the ability to set up the fritzbox_callmonitor integration via a config flow and adds the ability to import from YAML to a config entry.

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
sensor:
  - platform: fritzbox_callmonitor
    name: Phone
    username: my_username
    password: my_password
    phonebook: 0
    prefixes:
      - '+49'
      - '+4989'
      - '089'

Additional information

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

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

To help with the load of incoming pull requests:

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

[springstan]

I will add tests for this integration as soon as I am sure that this config flow satisfies all standards. Therefore any feedback or comments about the config flow and the integrations itself is greatly appreciated 😄

[Kane610]

I think if you can avoid a breaking change initially it's a good thing. You can do import from platforms to config entry just as well from the init https://github.com/home-assistant/core/pull/26587/files

[balloob]

Couple of changes necessary 👍 Already looking really good

[balloob]

Requires tests of the config flow to be added.

[springstan]

Removing the breaking change paragraph and label since this breaking change has been merged with #39995

[MartinHjelmare]

Nice! Some comments.

[MartinHjelmare]

We should return None explicitly in the last case.

[MartinHjelmare]

Normally the class name is patched and not the init method. Then the return value of that mock, of the class, can be specced with attributes that have return values or side effects as needed.

[MartinHjelmare]

The connect does blocking I/O by creating and connecting a socket. This needs to run in the executor via hass.async_add_executor_job.