Suggested test: copilot/push-tag-trigger

## Motivation

Link to gh-aw PR: github/gh-aw#45362 — Lock in tag-scoped `on.push` as a valid scoped trigger.

Tag-only push triggers (`on.push.tags`) were being incorrectly flagged as unscoped. The fix aligns the scope validator to accept tag-based filtering as a valid alternative to branch filtering. There is no existing E2E test verifying that a workflow with `on.push.tags` compiles and runs correctly.

## Proposed test

- **Workflow file**: `test-copilot-push-tag-trigger.md`
- **Trigger**: `workflow_dispatch` (for the test itself); the workflow-under-test uses `on.push.tags`
- **Engine**: copilot
- **Safe output**: `create-issue` (to signal the agent ran successfully)
- **Variant**: standard

## Minimal test prompt sketch

Ask the agent to create an issue confirming it was triggered by a tag push workflow. The compiled lockfile's `on:` block should include `push: tags: ['v*']` alongside `workflow_dispatch`, exercising the tag-scoped trigger path through the compiler and validator.

## New fixtures or secrets needed

None. Uses the existing `githubnext/gh-aw-test` repo. A tag push fixture is not needed for the dispatch-triggered E2E run itself — the key assertion is that the compiled `.lock.yml` includes the correct tag-scoped trigger and the workflow executes.

## Notes

The existing tests all use `on: workflow_dispatch` or issue/PR triggers. This would be the first test exercising a push-tag trigger in the frontmatter. Could eventually be paired with a `nosandbox` variant.

> [!WARNING]
>
> Firewall blocked 1 domain
>
> The following domain was blocked by the firewall during workflow execution:
>
> - `awmgmcpg`
>> To allow these domains, add them to the `network.allowed` list in your workflow frontmatter:
>
> ```yaml
> network:
> allowed:
> - defaults
> - "awmgmcpg"
> ```
>
> See [Network Configuration](https://github.github.com/gh-aw/reference/network/) for more information.
>
>

> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/29320519088) · 18.3 AIC · ⌖ 5.55 AIC · ⊞ 5.6K · [◷](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)

Start by reviewing the existing E2E tests that use workflow_dispatch and the proposed test-copilot-push-tag-trigger.md workflow. Add the copilot standard test with create-issue output, then verify compilation produces a .lock.yml whose on: block includes workflow_dispatch and push tags ['v*'], and that the workflow executes.

Written by the indexing model from the issue text.