Suggested test: copilot/comment-memory-config

## Motivation

Link to the gh-aw PR: github/gh-aw#51622 — expanded unit-test coverage for `comment-memory` map-form config fields (`max`, `memory-id`, `target`, `target-repo`, `allowed-repos`, `footer`), which are parsed by `parseCommentMemoryConfigValue`. These fields are only covered by Go unit tests today; there is no E2E workflow exercising `comment-memory` at all.

## Proposed test

- **Workflow file**: `test-copilot-comment-memory.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `add-comment` (with `comment-memory` map-form config: `memory-id`, `footer`)
- **Variant**: standard

## Minimal test prompt sketch

Configure `safe-outputs.add-comment.comment-memory` with a `memory-id` and custom `footer`, then have the agent post a comment on a fixture issue twice across two dispatches (or within one run posting to a known issue) and confirm the memory footer appears and updates/dedupes as expected on the second run.

## New fixtures or secrets needed

May need a persistent fixture issue number to comment against across runs, or the test can create+comment on a fresh issue within a single dispatch to keep it self-contained and avoid persistent-fixture complexity.

## Notes

No existing test file references `comment-memory` or `memory-id`. This is a genuinely new feature area (comment-level dedupe/memory), distinct from `cache-memory`/`restore-memory` already covered by `test-copilot-restore-memory-custom-job.md`. Open question: exact semantics of what "memory" changes on a second dispatch — may need triage before writing a compilable `.md`, so filing as an issue rather than a PR.

> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/31372362890) · auto · 44.6 AIC · ⌖ 2.52 AIC · ⊞ 8.3K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-test+is%3Aissue+%22gh-aw-workflow-call-id%3A+githubnext%2Fgh-aw-test%2Fsuggest-new-e2e-tests%22&type=issues)