Add already_in_progress to base strings for config flows

[springstan]

Breaking change

Proposed change

Adds already_in_progress to the base strings for config flows.
Uses this newly added base string in various integrations.

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

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue: Translations: extend config/option flow base strings #37263
• 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
• 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.

[probot-home-assistant]

This pull request needs to be manually signed off by @home-assistant/core before it can get merged.
_{^{(message by ReviewEnforcer)}}

[SNoof85]

"already_in_progress": "[%key:common::config_flow::abort::no_devices_found%]" should be "already_in_progress": "[%key:common::config_flow::abort::already_in_progress%]"

[springstan]

Thanks @SNoof85 for reviewing all of my PRs! I have fixed the wrong base string, probably a copy-paste error on my side.

[SNoof85]

As you're faster than me to create i'll do reviews 👀

[MartinHjelmare]

We (a Lokalise admin) should rename this key in existing translations in Lokalise.

[MartinHjelmare]

Please rebase again.