fix(@schematics/angular): format template files to match Prettier conf

[danymarques]

Applies consistent formatting to Angular schematic template files to prevent changes when Prettier is executed on freshly generated files. The templates now respect the formatting configuration defined in package.json.

PR Checklist

Please check to confirm your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

When we format a file using Prettier on a freshly generated project, it reads the configuration in the package.json and formats the file. It would be nice if the templates were already formatted correctly to avoid unnecessary git changes.

Issue Number: N/A

Templates are formatted following the configuration set in package.json

Does this PR introduce a breaking change?

• Yes
• No

Other information

[jkrems]

Thanks, I think this is a good idea overall! But in its current form, it does seem to break some of the additional variants that can be created (https://github.com/angular/angular-cli/actions/runs/16963647619/job/48160598107?pr=30916). I'm a bit concerned that this approach might not be fully generalizable because the correct formatting can change based on the exact options provided, e.g. optional imports or provider array elements.

That said, I'd be happy to merge this kind of formatting-only change assuming that the build passes.