#2559 Docs: auth token revoke deletes the token, but the manual says it stays in the token list

The manual describes swamp auth token revoke as a soft revoke, but the CLI performs a hard delete.

What the manual says

• content/manual/reference/api-key-authentication.md, section swamp auth token revoke: "A revoked token can no longer authenticate requests but remains visible in the token list." The swamp auth token list section above it also says "Revoked tokens appear with enabled: false in JSON output."
• content/manual/how-to/authenticate-with-api-keys.md, "Revoke a collective token from the CLI": "Use swamp auth token revoke to disable a token ... A revoked token remains visible in the token list but can no longer authenticate requests." The later "Revoke a key" section says the CLI command will "disable it".

What actually happens

swamp auth token revoke <id> --collective <c> sends DELETE /api/v1/collectives/<c>/api-tokens/<id>. swamp-club handles that with deleteCollectiveApiToken, which removes the record. Afterwards the token no longer appears in swamp auth token list at all, and its key is rejected. The soft path (disable, keep the record, show enabled: false) is the PATCH on the same route (revokeCollectiveApiToken), which the web UI's Revoke button uses. The CLI does not.

Observed against swamp-club 79b28281 while reproducing lab #2555.

Suggested change

In both pages, describe the CLI revoke as permanently removing the token: it disappears from swamp auth token list and its key stops working. Keep the enabled: false note only where it applies, i.e. to tokens disabled with Revoke in the web UI. If the CLI later moves to a soft delete, the wording will need revisiting; the CLI verb stays revoke either way.