Suppress no-op tracking issue posts from bump-tcgc-csharp workflow (#10517)

The daily `bump-tcgc-csharp` agentic workflow posts to the No-Op
tracking issue (#10516) on every run where no newer stable TCGC release
is available, which is the common case and creates noise.

### Changes

- **`.github/workflows/bump-tcgc-csharp.md`** — Opt out of no-op
reporting by setting `safe-outputs.noop.report-as-issue: false`.
- **`.github/workflows/bump-tcgc-csharp.lock.yml`** — Updated to reflect
the source change:
- Embedded `noop` handler config blobs flip `report-as-issue` from
`"true"` to `"false"`.
- `GH_AW_NOOP_REPORT_AS_ISSUE` env var on the `Process no-op messages`
step in the `conclusion` job flipped from `"true"` to `"false"`. This is
the env var actually consumed by `handle_noop_message.cjs` to decide
whether to post to the `[aw] No-Op Runs` tracking issue, and was the
reason a follow-up run (#10518) was still posting after the initial fix.

```yaml
safe-outputs:
  messages:
    footer: ">  Generated by [{workflow_name}]({run_url})"
    footer-install: "<!-- -->"
  noop:
    report-as-issue: false
  create-issue:
    ...
```

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: jorgerangel-msft <102122018+jorgerangel-msft@users.noreply.github.com>
Co-authored-by: Jorge Rangel <jorgerangel@microsoft.com>

Author: Copilot

.github/workflows/bump-tcgc-csharp.lock.yml

@@ -17,6 +17,8 @@ safe-outputs:
   messages:
     footer: ">  Generated by [{workflow_name}]({run_url})"
     footer-install: "<!-- -->" # Need this as empty string will still include it
+  noop:
+    report-as-issue: false
   create-issue:
     title-prefix: "Bump TCGC to "
     labels: [emitter:client:csharp]