Prevent async_create_entry from reauth/reconfigure flows

[epenet]

Breaking change

Use of async_create_entry within reauth and reconfigure flow causes new config entries to be created.
If an existing entry exists with the same unique_id, it will also cause the previous entry to be removed.

This invalid use of async_create_entry will be blocked from 2025.11.
Please refactor to use async_update_reload_and_abort or async_abort with a valid reason (eg. reauth_successful, reconfigure_successful, ...)

Proposed change

Tests have been added to highlight the behavior.

Sample run raising ValueError on core: https://github.com/home-assistant/core/actions/runs/11176114641

Violations fixed in:

• Use reauth helpers in permobil config flow #127530
• Use reauth helpers in spotify config flow #127532
• Use reconfigure helpers in config tests #127534

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:
• Link to documentation pull request:

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.

To help with the load of incoming pull requests:

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

[emontnemery]

I think we should not say "can cause unexpected behavior", I think we should say we want reconfigure and reauth flows to update an existing entry and then abort, not create a new entry.

[epenet]

Message updated

[emontnemery]

We should update developer documentation to explain reconfigure and reauth flows are expected to update an existing entry and then abort:

• https://developers.home-assistant.io/docs/config_entries_config_flow_handler#reconfigure
• https://developers.home-assistant.io/docs/config_entries_config_flow_handler#reauthentication

[epenet]

We should update developer documentation to explain reconfigure and reauth flows are expected to update an existing entry and then abort:

• https://developers.home-assistant.io/docs/config_entries_config_flow_handler#reconfigure
• https://developers.home-assistant.io/docs/config_entries_config_flow_handler#reauthentication

I created a docs PR home-assistant/developers.home-assistant#2352

I have also adjusted the error message and the PR description.