Update pay-x402 extension entry to v1.1.0

[shawn93676]

Updates the pay-x402 entry in extensions/catalog.community.json from v1.0.0 to v1.1.0.

Why this matters: the catalog currently serves v1.0.0, whose pay command directed agents to POST to an endpoint that is itself a paid x402 resource — an agent following the bundled instructions received a 402 instead of a payment header. v1.1.0 fixes the flow (the payer signs its own payment) and removes XRPL claims the facilitator never supported.

Changes:

• version: 1.0.0 → 1.1.0
• download_url: points at the v1.1.0 tag (verified: the zip resolves)
• description: updated to match v1.1.0 (spend caps, counterparty credit check via SolvScore, x402 payments during spec implementation; settles on Base or Solana)
• updated_at: entry-level and catalog-level timestamps

Follows the Extension Submission template (filed as issue #4446 on Sept 4); the catalog was last refreshed Sept 3, so the entry has not yet picked up the v1.1.0 fix.

Tag: 🤖🤖🤖 (prepared by an AI agent on behalf of the extension author, per repo convention).

[mnriem]

Thanks — but catalog changes shouldn't be hand-edited into catalog.community.json via a PR; they go through the [Extension] submission-issue flow, which validates the release/digests and generates the catalog PR automatically. Good news: you already filed this correctly as #4446, so this PR is a duplicate of that submission. Closing this in favor of #4446 — the v1.1.0 update will land through the automated pipeline there. (No need to also open the PR; the issue is enough.)