fix(@schematics/angular): remove CommonModule import from standalone components

[cexbrayat]

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 new behavior?

ng g c no longer generates a component with the CommonModule import. This import is not useful if developers adopt the control flow syntax in their templates. Instead, developers are encouraged to import the individual directives/pipes if needed.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[clydin]

I think it's also important to note that the Angular compiler will generate an actionable error message in the event that a developer attempts to use one of the directives with these changes. For example:

NG8103: The `*ngFor` directive was used in the template, but neither the `NgFor` directive
nor the `CommonModule` was imported. Use Angular's built-in control flow @for or make sure
that either the `NgFor` directive or the `CommonModule` is included in the `@Component.imports`
array of this component.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}