Revert fetching config flow after subscribe for progress

[bramkragten]

Reverts #18775

Breaking change

The original PR was created for home-assistant/core#71034, that will have a timing issue again.

Proposed change

This change, while technically probably correct, causes issues with flows, we are going to revert this for now, check all the config flows and fix them, and afterwards re-enable this.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• 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

[emontnemery]

I don't agree with this PR.

#18775 fixed a fundamental flaw in the show progress functionality.
It should always be possible to refetch a flow. If it isn't, that's a bug in the flow where it incorrectly does not track its state.