build: group commits by package name in changelog (#23460)

Currently the new release tooling groups changes in the
changelog based on their commit scope. This is the default
behavior that works well for FW and the CLI repo.

For the components repository, we also include secondary entry-point
information in commit messages. This currently results in
many unnecessary groups, while ideally we'd want to group
based on the package name in the scope. This commit implements
that.

(cherry picked from commit 9aa21dc)

Author: devversion

.ng-dev/release.ts

@@ -71,13 +71,28 @@ export const releasePackages = [
 
 /** Configuration for the `ng-dev release` command. */
 export const release: ReleaseConfig = {
-  releaseNotes: {useReleaseTitle: true, groupOrder: releasePackages},
+  releaseNotes: {
+    useReleaseTitle: true,
+    groupOrder: releasePackages,
+    categorizeCommit: commit => {
+      const [packageName, entryPointName] = commit.scope.split('/');
+      const entryPointPrefix = entryPointName ? `**${entryPointName}:** ` : '';
+
+      // In the `angular/components` repository, commit messages may include entry-point
+      // information in the scope. We expect commits to be grouped based on their package
+      // name. Commits are then described with their subject and optional entry-point name.
+      return {
+        groupName: packageName,
+        description: `${entryPointPrefix}${commit.subject}`,
+      };
+    },
+  },
   publishRegistry: 'https://wombat-dressing-room.appspot.com',
   npmPackages: releasePackages.map(pkg => `@angular/${pkg}`),
   buildPackages: async () => {
     // The `performNpmReleaseBuild` function is loaded at runtime as loading of the
     // script results in an invocation of Bazel for any `yarn ng-dev` command.
     const {performNpmReleaseBuild} = await import('../scripts/build-packages-dist');
     return performNpmReleaseBuild();
-  }
+  },
 };