fix(@angular/cli): correctly handle --collection option in ng new

Previously, this option was ignored due to an incorrect deconstruction.

Closes #23414

(cherry picked from commit 5a012b5)

Author: alan-agius4

packages/angular/cli/src/commands/new/cli.ts

@@ -45,7 +45,7 @@ export class NewCommandModule
     });
 
     const {
-      options: { collectionNameFromArgs },
+      options: { collection: collectionNameFromArgs },
     } = this.context.args;
 
     const collectionName =

tests/legacy-cli/e2e/tests/commands/ng-new-collection.ts

@@ -0,0 +1,19 @@
+import { execAndWaitForOutputToMatch } from '../../utils/process';
+
+export default async function () {
+  const currentDirectory = process.cwd();
+
+  try {
+    process.chdir('..');
+
+    // The below is a way to validate that the `--collection` option is being considered.
+    await execAndWaitForOutputToMatch(
+      'ng',
+      ['new', '--collection', 'invalid-schematic'],
+      /Collection "invalid-schematic" cannot be resolved/,
+    );
+  } finally {
+    // Change directory back
+    process.chdir(currentDirectory);
+  }
+}