Add configuration flow to CPU Speed

[frenck]

Breaking change

The CPU Speed integration migrated to configuration via the UI. Configuring CPU Speed via YAML configuration has 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

This PR implements the bare minimum configuration flow for the CPU Speed integration, including import.

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

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Add configuration flow to CPU Speed home-assistant.io#20910

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.

[probot-home-assistant]

Hey there @fabaff, mind taking a look at this pull request as it has been labeled with an integration (cpuspeed) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[bdraco]

Suggested change

"title": "CPU Speed",

Not needed since its the same as the manifest

[frenck]

Incorrect, this is an integration that is perfectly fit for offering translation on the title.

[bdraco]

Suggested change

"title": "CPU Speed"

[frenck]

Same as above

[bdraco]

Should this abort if the install type is in a container ?

[frenck]

Should this abort if the install type is in a container ?

Maybe, I'm looking at those cases in the next steps.

[bdraco]

Should this abort if the install type is in a container ?

Maybe, I'm looking at those cases in the next steps.

In case its mildly helpful, this is what usb is using

        info = await system_info.async_get_system_info(self.hass)
        if info.get("docker"):
            return

[MartinHjelmare]

already_configured

[frenck]

👍 #63284