fix(ng-dev/release): improve lockfile exclusion logic in snapshot publishing

Update the snapshot publishing logic to more robustly exclude lockfiles from
determining if a snapshot is affected by changes.

Specifically:
- Added pnpm-lock.yaml to the list of excluded paths.
- Added both root-level and glob variants for MODULE.bazel.lock, pnpm-lock.yaml, and pubspec.lock.
- Wrapped exclude pathspecs in quotes to ensure they are correctly interpreted by the git command.

Author: alan-agius4

ng-dev/release/snapshot-publish/snapshots.ts

@@ -34,7 +34,16 @@ interface SnapshotRepo {
 /**
  * Paths to exclude from the snapshot commit.
  */
-const PATHS_TO_EXCLUDE = ['**/MODULE.bazel.lock', '**/package-lock.json', '**/pubspec.lock'];
+const PATHS_TO_EXCLUDE = [
+  'MODULE.bazel.lock',
+  '**/MODULE.bazel.lock',
+
+  'pnpm-lock.yaml',
+  '**/pnpm-lock.yaml',
+
+  'pubspec.lock',
+  '**/pubspec.lock',
+];
 
 export class SnapshotPublisher {
   /** The current branch name. */
@@ -171,7 +180,7 @@ export class SnapshotPublisher {
               'HEAD',
               '--',
               '.',
-              ...PATHS_TO_EXCLUDE.map((p) => `:(exclude)${p}`),
+              ...PATHS_TO_EXCLUDE.map((p) => `':(exclude)${p}'`),
             ],
             {cwd: tmpRepoDir},
           ).status === 1;