Fix scaffolding generations

[stevenh]

Proposed change

Fix script.scaffold generation which is not integration for example config_flow which was failing due to hassfest quality check.

Fix config_flow_helper which would generate out of order manifest keys due to lack of sorting.

This moves the sort_manifest from to script.util as it's now used in multiple scripts.

This updates all flows to pass the integration path to hassfest, so it only checks the integration it's working on and skips the quality check which will fail on newly 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)
• 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 fixes the issue flagged by @balloob here

I've tested that all templates for script.scaffold successfully generate a new integration without error.

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.

[stevenh]

@balloob here's the fix for the additional issue you mentioned on my previous PR

[MartinHjelmare]

For the future, please don't squash or amend commits after review has started to make it easier for readers to track changes.

[stevenh]

For the future, please don't squash or amend commits after review has started to make it easier for readers to track changes.

Thanks for info, different teams work differently 😄

Do you prefer merge commits or Update branch from the github UI?

Any other preferences I can read up on?

[MartinHjelmare]

Rebasing and merging, to update the branch, are both ok, but I think most people prefer merge since history isn't lost. We'll squash when merging the PR, so it doesn't matter for the result in the target branch. It's fine to press the update branch button in the GitHub web UI.