Add config flow to Russound RIO integration

[noahhusby]

Proposed change

I'm working on improving the stability of the Russound RIO integration. This is part one of a set of pull requests with feature improvements. This PR is dedicated to adding a config flow and adjacent tests to make the integration simpler to setup. I plan to add proper connection error handling, multi-instance capability, and expand the usage of the RIO protocol in coming pull requests. This includes a YAML importer for existing configurations so that this doesn't result in a breaking-change.

The config flow currently only supports a single instance (as defined in the manifest). I will be opening a PR for multi-instance support soon, but wanted to keep this PR dedicated for adding the config flow only.

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)
• Deprecation (breaking change to happen in the future)
• 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: N/A
• This PR is related to issue: N/A
• Link to documentation pull request: Update Russound RIO integration to reflect migration to config flow home-assistant.io#33574

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
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format 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.

To help with the load of incoming pull requests:

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

[home-assistant]

Hi @noahhusby

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[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.

Stale

[jpbede]

First of thanks a lot for your contribution 🚀

Take a look at mpd, for example, to see how you can import the existing configuration into a config entry. In this way, you avoid having a breaking change.

[noahhusby]

Thought about adding the YAML importer late last night, glad you caught it too 👍

We can remove the breaking-change label.

Note: I noticed that the .coveragerc was removed today. Not sure if the intention is only to get a more accurate coverage report, or to have all integration files covered. My media player file doesn't have a test file at the moment, but I intend to add that in a separate PR to not lose scope of the config flow.

Changes fixed