Mint, scope and rotate Turso database and group auth tokens

Documented steps

1. Choose scope. Database token = one database. Group token = every database in the group, which is what you want for multi-tenant fleets where databases are created continuously.
2. Database token via CLI: `turso db tokens create <database-name>` with `-e/--expiration <never|7d|7d3h2m1s>` and `-r/--read-only` (https://docs.turso.tech/cli/db/tokens/create).
3. Database token via API: POST https://api.turso.tech/v1/organizations/{organizationSlug}/databases/{databaseName}/auth/tokens with query params `expiration` and `authorization` (full-access | read-only) (https://docs.turso.tech/api-reference/databases/create-token).
4. Group token via CLI: `turso group tokens create <group-name>`; via API: POST https://api.turso.tech/v1/organizations/{organizationSlug}/groups/{groupName}/auth/tokens (https://docs.turso.tech/api-reference/groups/create-token).
5. For finer control, use fine-grained permission claims (e.g. all:data_read, or per-table data_add/data_update) rather than issuing a full-access token to an untrusted client (https://docs.turso.tech/sdk/authorization/tokens).
6. Set an explicit expiration for anything shipped to a client or CI runner — the documented DEFAULT is `never`.
7. To revoke: POST https://api.turso.tech/v1/organizations/{organizationSlug}/databases/{databaseName}/auth/rotate, which invalidates all existing tokens for that database (https://docs.turso.tech/api-reference/databases/invalidate-tokens).
8. Re-mint and redeploy tokens to every consumer immediately after rotating, then verify with a read query over /v2/pipeline.