Add Repair next flow as repair flow

[iluvdata]

Breaking change

None anticipated. 🤞🏻

Proposed change

• Add support for issue repair flows to support next_flow being another repair flow as discussed in Add next_flow to Repair Flows core#165091 (comment)
• Remove frontend requirement for the step.type to be create_entry to allow abort as well which is how the backend implements next flows in Config Entry Flows, Options Flows, and Subentry Config Flows. See async_abort in ConfigFlow.

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

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request:
• Link to developer documentation pull request: Document next_flow in async_create_entry in RepairsFlow developers.home-assistant#2985
• Link to backend pull request: Add next_flow to Repair Flows core#165091

Checklist

• I understand the code I am submitting and can explain how it works.
• The code change is tested and works locally.
• There is no commented out code in this PR.
• I have followed the perfect PR recommendations
• 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

To help with the load of incoming pull requests:

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

[iluvdata]

This check is not needed plus the backend supports _step.type === "abort".

Same with Subentry and Option flows.