Name automation templates after the action, not the agent

[VascoSch92]

Desired Behavior

Automation template cards should be named after the action the automation performs, not after the agent that performs it. Three catalog entries in automations/catalog/ are currently named after an agent:

id	current name
github-issue-to-pr	GitHub Issue to PR Agent
github-pr-reviewer	GitHub Code Review Agent
qa-changes	QA Changes Agent

Every other entry already reads as the work it does (GitHub repository monitor, Linear issue triage assistant, Upstream fork sync, Daily news digest). These three are also the only Title Case names in the catalog, so they stand out twice over. The entry name is what Agent Canvas prints on the template card and what a created automation is named after, so the mention surfaces to every user setting one up.

AGENTS.md Maintainer should stay as it is: that is the name of a file, not an agent mention.

Acceptance Criteria

• automations/catalog/github-issue-to-pr/manifest.json, automations/catalog/github-pr-reviewer/manifest.json, and automations/catalog/qa-changes/manifest.json carry names that describe the action and contain no Agent mention.
• The new names follow the sentence-case convention the rest of the catalog uses.
• The worked example in automations/README.md quotes the updated github-pr-reviewer name.
• tests/fixtures/automations/github-pr-reviewer.json is updated, since test_automation_setup.py derives the created automation's name from the entry name and compares the request body to those fixtures byte for byte.
• uv run --group test pytest passes.

[github-actions]

✅ ready-for-dev label applied

This issue meets the readiness criteria and is ready for contribution.
A contributor can now open a PR that links this issue (Fixes #<number>).

This is an automated readiness check posted by a workflow.