Map invocation lifecycle files to CLI regression scenarios

## Summary

Update the Foundry extension's PR impact mapping so changes to the unified invocation lifecycle commands select the relevant offline regression scenarios.

This documentation-only follow-up was split from #9900 and #9901 to keep the separate `.github/` approval requirement out of the feature PRs.

## Acceptance criteria

Update `.github/skills/foundry-extension-scenario-pr-regression/references/impact-mapping.md` with:

- `internal/cmd/invocations*.go` → `cmd:invocations`
- `internal/cmd/invoke_response*.go` → `cmd:invoke`, `cmd:invocations`
- `internal/cmd/invoke_invocation*.go` → `cmd:invoke`, `cmd:invocations`

Preserve existing line endings so the diff remains three added rows. No production code, provisioning, or new live-test infrastructure is required.

Implementation: #9996.
Related feature tracking: #9676. This issue tracks only the regression mapping, not completion of the broader feature.

Open .github/skills/foundry-extension-scenario-pr-regression/references/impact-mapping.md and review the existing mappings for invocation commands. Add the three specified rows, preserve the existing line endings, and confirm the diff contains only those three added rows; no production code or live-test infrastructure is needed.

Written by the indexing model from the issue text.