Fix otbr flaky config flow tests in Python 3.14.3

[epenet]

Breaking change

Proposed change

Spotted in https://github.com/home-assistant/core/actions/runs/25039807993/job/73341207506?pr=162263 and needed for #162263.

The tests test_hassio_discovery_flow_router_not_setup and test_hassio_discovery_flow_router_not_setup_has_preferred fail under Python 3.14.3 with:

AttributeError: 'ConfigEntry' object has no attribute 'runtime_data'

Both tests use the multiprotocol URL http://core-silabs-multiprotocol:8081 and patch async_setup_entry to return True without setting runtime_data. When the flow exercises the _set_dataset path it calls get_allowed_channel, which lazily initializes the MultiprotocolAddonManager. Once otbr's component_loaded event fires, the manager's platform callback iterates loaded entries and dereferences config_entry.runtime_data — which the mock never set — raising the AttributeError.

Fix by adding the existing multiprotocol_addon_manager_mock fixture (already used by test_hassio_discovery_flow_router_not_setup_has_preferred_2) so the manager singleton is pre-installed and the platform discovery callback never runs.

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: fixes #
• This PR is related to issue: Bump base image to 2026.02.0 with Python 3.14.3, use 3.14.3 in CI #162263
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• 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][dev-checklist]
• I have followed the [perfect PR recommendations][perfect-pr]
• The code has been formatted using Ruff (`ruff format homeassistant tests`)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for [www.home-assistant.io][docs-repository]

If the code communicates with devices, web services, or third-party tools:

• The [manifest file][manifest-docs] 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 diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

🤖 Generated with Claude Code

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (otbr) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of otbr can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant mark-draft Mark the pull request as draft.
• @home-assistant ready-for-review Remove the draft status from the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign otbr Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant update-branch Update the pull request branch with the base branch.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the pull request.

[Copilot]

Pull request overview

This PR fixes flaky OTBR config flow tests on Python 3.14.3 by ensuring the Silicon Labs Multiprotocol add-on manager is pre-seeded in hass.data, preventing a late platform callback from accessing missing ConfigEntry.runtime_data in a mocked setup path.

Changes:

• Add the existing multiprotocol_addon_manager_mock fixture to two hassio discovery flow tests to avoid lazy manager initialization side effects.