fix: align community submission workflows with bug-assess label trigger (#3046)

The add-community-extension and add-community-preset agentic workflows
never ran for real submissions. Their issue templates auto-applied the
`extension-submission`/`preset-submission` label at creation, which lands
in the `opened` event (not `labeled`), and the external submitter fails
the team-membership activation gate.

Align both with the working bug-assess pattern:
- Add `names: [extension-submission]` / `[preset-submission]` so a
  job-level condition gates activation on the specific label.
- Add `github: min-integrity: none` to allow reading external user issues.
- Remove the trigger label from the issue-template auto-labels so a
  maintainer applies it during triage — emitting a real `labeled` event
  from a team member, which passes activation.
- Recompile lock files with gh aw v0.79.8.

Co-authored-by: Manfred Riem <mnriem@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

.github/workflows/add-community-extension.md

@@ -5,6 +5,7 @@ emoji: "🧩"
 on:
   issues:
     types: [labeled]
+    names: [extension-submission]
   skip-bots: [github-actions, copilot, dependabot]
 
 tools:
@@ -12,6 +13,7 @@ tools:
   bash: ["echo", "cat", "head", "tail", "grep", "wc", "sort", "python3", "jq", "date"]
   github:
     toolsets: [issues, repos]
+    min-integrity: none
   web-fetch:
 
 permissions:
@@ -49,8 +51,10 @@ or update entries in the community extension catalog.
 
 ## Triggering Conditions
 
-This workflow only triggers when the `extension-submission` label is added to an
-issue. Before processing, verify that the issue title starts with `[Extension]:`.
+This workflow is triggered by any `issues: labeled` event, but a job-level
+condition gates the agent run so it only proceeds when the label that was just
+added is `extension-submission`. By the time you run, that condition has already
+passed. Before processing, verify that the issue title starts with `[Extension]:`.
 If it does not, stop without commenting.
 
 ## Step 1 — Read and Parse the Issue

.github/workflows/add-community-preset.md

@@ -5,6 +5,7 @@ emoji: "🎨"
 on:
   issues:
     types: [labeled]
+    names: [preset-submission]
   skip-bots: [github-actions, copilot, dependabot]
 
 tools:
@@ -12,6 +13,7 @@ tools:
   bash: ["echo", "cat", "head", "tail", "grep", "wc", "sort", "python3", "jq", "date"]
   github:
     toolsets: [issues, repos]
+    min-integrity: none
   web-fetch:
 
 permissions:
@@ -49,8 +51,10 @@ or update entries in the community preset catalog.
 
 ## Triggering Conditions
 
-This workflow only triggers when the `preset-submission` label is added to an
-issue. Before processing, verify that the issue title starts with `[Preset]:`.
+This workflow is triggered by any `issues: labeled` event, but a job-level
+condition gates the agent run so it only proceeds when the label that was just
+added is `preset-submission`. By the time you run, that condition has already
+passed. Before processing, verify that the issue title starts with `[Preset]:`.
 If it does not, stop without commenting.
 
 ## Step 1 — Read and Parse the Issue