[runtime] serve commons verbs on v1.1.0 routes

[GsCommand]

Motivation

• Bring the live runtime route surface and runtime-discovery metadata into alignment with the Commons v1.1.0 release so enabled verbs are served on real v1.1.0 routes.
• Keep existing behavior for /health, /verify, signer identity, and ENS verification while changing only the route/version defaults and minimal test/script fixtures.

Description

• Change the runtime defaults in server.mjs by setting API_VERSION and SERVICE_VERSION to "1.1.0" so the mounted verb routes resolve to POST /<verb>/v1.1.0 instead of v1.0.0.
• Replace hardcoded fallback x402 version/entry strings and the describe response version property to use the API_VERSION constant so generated receipts and entries reflect v1.1.0.
• Leave route mounting logic unchanged (app.post(/${verb}/v${API_VERSION})) so the endpoint style is preserved, and explicitly avoid touching /verify, /health, signer logic, ENS resolution, or schema validation behaviors.
• Update repo-local smoke and unit test fixtures and helper scripts to exercise the new routes and default x402 values by editing tests/smoke.mjs, runtime/tests/runtime-signing.test.mjs, scripts/smoke.mjs, and scripts/smoke-ens.sh.

Testing

• Ran npm test which executed the unit suite and produced 15 passing tests and 1 failing test (boot fails fast without keys unless DEV_AUTO_KEYS=1) due to the spawned process output not meeting the test's assertion in this environment.
• Ran the integration smoke script with node tests/smoke.mjs which completed successfully and verified /health, a POST /describe/v1.1.0 execution, and a /verify roundtrip.
• No changes were made to /health or /verify implementation and signer/ENS behavior was not modified; the tests above confirm the new v1.1.0 verb surface is reachable by the smoke checks.

---

Codex Task