fix(cli): Silence set-commits repository errors in issue reporting (#2151)

## Summary

0.48.0 made `release set-commits --auto` read the repository from CI
variables and match it by name. The failures that are left on 0.48/0.49
are org setup problems, and they are still captured as Sentry issues:

- **`repository` field (CLI-17R):** `--auto` finds no repository, for
example on a Vercel preview build or a Docker build without `.git` and
without CI repository variables. Or the org has not added the matching
repository in Sentry. This came to about 440 events on 0.48.0 and 0.49.0
over 30 days.
- **`commit.repository` field (CLI-4G3, formerly CLI-2SK):** a
`--commit` repository that the org doesn't have in Sentry, or an org
with no repositories at all. This came to about 46 events on 0.49.0.

The user gets an error that says how to fix it in each case. Most of
these runs come through the bundler plugins with
`shouldNotThrowOnFailure`, so builds keep going.

### Key Changes

- `classifySilenced` treats `ValidationError`s with field `repository`
or `commit.repository` as `user_validation`. Other `ValidationError`s
and API errors from the same flow are still captured.
- `cli.error.silenced` now records `validation_field` for silenced
`ValidationError`s. That keeps the volume of each case measurable after
it stops creating issues.

<!-- junior-request-attribution:start -->
via @betegon.
<!-- junior-request-attribution:end -->

<!-- junior-session-footer:start -->
<!-- junior-conversation-id:agent%3A13af9393ba498bf4b925a816a4a5290f -->

--

[View Session in
Sentry](https://sentry.sentry.io/explore/conversations/agent%3A13af9393ba498bf4b925a816a4a5290f/?project=4510944073809921)

<!-- junior-session-footer:end -->

Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
Co-authored-by: bete <28983162+betegon@users.noreply.github.com>

Author: sentry-junior[bot]

packages/cli/src/lib/error-reporting.ts

@@ -137,6 +137,18 @@ export function classifySilenced(error: unknown): SilenceReason | null {
   ) {
     return "user_validation";
   }
+  // A ValidationError with field "repository" or "commit.repository" means
+  // `release set-commits` could not match a Sentry repository: the build has
+  // no git remote or CI repository variables (Vercel preview, Docker without
+  // .git), or the org has not added the repository (CLI-17R, CLI-4G3). The
+  // org's setup has to change, and the user sees how to fix it. The
+  // `cli.error.silenced` metric keeps the volume, split by `validation_field`.
+  if (
+    error instanceof ValidationError &&
+    (error.field === "repository" || error.field === "commit.repository")
+  ) {
+    return "user_validation";
+  }
   // A ValidationError with field "input" means the --input file path the user
   // supplied does not exist on disk. Pure user-input noise, not a CLI bug —
   // the user sees a clear "File not found" message (CLI-1JY).
@@ -198,6 +210,9 @@ function recordSilencedError(error: unknown, reason: SilenceReason): void {
   if (error instanceof SeerError) {
     attributes.seer_reason = error.reason;
   }
+  if (error instanceof ValidationError && error.field) {
+    attributes.validation_field = error.field;
+  }
 
   // oxlint-disable-next-line sentry-cli/no-silent-catch -- grandfathered silent catch — see #1531; drain by adding log.debug()/log.warn() or re-throwing.
   try {

packages/cli/test/lib/error-reporting.test.ts

@@ -366,6 +366,27 @@ describe("classifySilenced", () => {
     ).toBe("user_input_error");
   });
 
+  test.each([
+    [
+      "repository",
+      "Could not determine the repository: there is no 'origin' git remote and no CI repository variables.",
+    ],
+    ["repository", "No Sentry repository matching 'owner/repo' (from CI)."],
+    [
+      "commit.repository",
+      "Sentry organization 'my-org' has no repository named 'owner/repo'.",
+    ],
+  ])(
+    "silences set-commits ValidationError with field '%s' (CLI-17R, CLI-4G3)",
+    (field, message) => {
+      // The org's setup has to change (no repository in the build, or the
+      // repository isn't added in Sentry); it is not a CLI bug.
+      expect(classifySilenced(new ValidationError(message, field))).toBe(
+        "user_validation",
+      );
+    },
+  );
+
   test("silences ResolutionError (user provided a value that wasn't found)", () => {
     expect(
       classifySilenced(
@@ -645,6 +666,24 @@ describe("reportCliError integration", () => {
     );
   });
 
+  test("silences set-commits repository ValidationError and records the field", () => {
+    reportCliError(
+      new ValidationError("No Sentry repository matching 'a/b'.", "repository"),
+    );
+    expect(captureSpy).not.toHaveBeenCalled();
+    expect(metricSpy).toHaveBeenCalledWith(
+      "cli.error.silenced",
+      1,
+      expect.objectContaining({
+        attributes: expect.objectContaining({
+          error_class: "ValidationError",
+          reason: "user_validation",
+          validation_field: "repository",
+        }),
+      }),
+    );
+  });
+
   test("captures SeerError (marketing dashboard)", () => {
     reportCliError(new SeerError("not_enabled", "my-org"));
     expect(captureSpy).toHaveBeenCalled();