fix(a2a): publish reachable specification URLs

[FanouZeng-TT]

Description

The A2A business agent and chat client publish runtime UCP profiles containing
specification URLs with an obsolete shopping path segment:

https://ucp.dev/2026-01-23/specification/shopping/checkout

The service, checkout, fulfillment, and discount variants all return HTTP 404.
Their published 2026-01-23 counterparts without that segment—using
specification/overview for the service—return HTTP 200.

These files are served or consumed at runtime: the business agent returns
ucp.json from /.well-known/ucp, validates agent_card.json, and the chat
client advertises agent_profile.json in its UCP-Agent header.

Fix: replace the stale service and capability links in all three runtime
profiles with the reachable URLs for the same pinned version.

Category (Required)

• Core Protocol: Changes to the base communication layer, global context, or breaking refactors. (Requires Technical Council approval)
• Governance/Contributing: Updates to GOVERNANCE.md, CONTRIBUTING.md, or CODEOWNERS. (Requires Governance Council approval)
• Capability: New schemas (Discovery, Cart, etc.) or extensions. (Requires Maintainer approval)
• Documentation: Updates to README, or documentations regarding schema or capabilities. (Requires Maintainer approval)
• Infrastructure: CI/CD, Linters, or build scripts. (Requires DevOps Maintainer approval)
• Maintenance: Version bumps, lockfile updates, or minor bug fixes. (Requires DevOps Maintainer approval)
• SDK: Language-specific SDK updates and releases. (Requires DevOps Maintainer approval)
• Samples / Conformance: Maintaining samples and the conformance suite. (Requires Maintainer approval)
• UCP Schema: Changes to the ucp-schema tool (resolver, linter, validator). (Requires Maintainer approval)
• Community Health (.github): Updates to templates, workflows, or org-level configs. (Requires DevOps Maintainer approval)

Related Issues

N/A

Checklist

• I have followed the Contributing Guide (including Conventional Commits title requirements and ! for breaking changes).
• I have updated the documentation (if applicable).
• My changes pass all local linting and formatting checks.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• (For Core/Capability) I have included/updated the relevant JSON schemas.
• I have regenerated Python Pydantic models by running generate_models.sh under python_sdk.

Screenshots / Logs (if applicable)

• Old service/capability specification URLs: HTTP 404
• Updated overview, checkout, fulfillment, and discount URLs: HTTP 200
• All three runtime profiles parse as JSON
• uvx pre-commit run --all-files
• git diff --check