ci: drop paths filter from go-ci + perf-gate

Same trap that hit ci-java.yml during phase 5 (PR #131). When a
workflow's job name is a required check on branch protection AND the
workflow has a `paths:` filter, PRs that don't match the filter cause
the workflow to be SKIPPED. Skipped workflows never report a status,
so the required check sits in "Waiting for status to be reported"
indefinitely and blocks merge.

The cutover PR (#132) deletes Java but doesn't touch `go/**`, so both
`go-ci` and `perf-gate` were skipping with the old filter. Removing
the filter makes the jobs always run.

Cost: ~2 min go-ci, ~1 min perf-gate on docs-only PRs. Cheap.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: aksOps

.github/workflows/go-ci.yml

@@ -3,10 +3,14 @@ name: go-ci
 on:
   push:
     branches: [main]
-    paths: ['go/**', '.github/workflows/go-ci.yml']
   pull_request:
     branches: [main]
-    paths: ['go/**', '.github/workflows/go-ci.yml']
+  # No `paths:` filter — branch protection requires this job name. A
+  # path filter would cause skip-on-no-go-changes, which never reports
+  # a status and deadlocks "Waiting for status to be reported" (same
+  # trap that hit ci-java.yml before its filter was dropped, and that
+  # blocked PR #131). Go build + test is ~2 minutes with the module
+  # cache; cheap enough to always run.
 
 permissions:
   contents: read

.github/workflows/perf-gate.yml

@@ -13,14 +13,12 @@ name: perf-gate
 on:
   push:
     branches: [main]
-    paths:
-      - 'go/**'
-      - '.github/workflows/perf-gate.yml'
   pull_request:
     branches: [main]
-    paths:
-      - 'go/**'
-      - '.github/workflows/perf-gate.yml'
+  # No `paths:` filter — same reason as go-ci.yml. If branch protection
+  # ever marks this required, a path filter would deadlock "Waiting for
+  # status to be reported" on non-Go PRs. Wall-clock is ~1 minute; the
+  # signal is worth the cost.
   workflow_dispatch:
 
 permissions: