GET /api/v1/tokens carries an ETag and answers a repeat with 304 until a token is made, used or revoked #9199

The owner's tokens page and agents re-reading the token list pay a header, not a body, while no token changed.

Done looks like:

• [x] The /api/v1/tokens route in src/http/api/tokens.ts answers 200 with a weak etag from weakEtag (src/http/etag.ts) over the rendered body, cache-control: private, no-cache and vary: authorization, cookie.
• [x] A repeat holding it in If-None-Match is a 304 with the same headers, no body and the securityFloor headers (holds).
• [x] The etag moves when a token is created, revoked, or its last-used time or client changes; two viewers who are shown different bodies never share an etag.
• [x] No session or account answer exactly as today, with no ETag, even with If-None-Match: *; the 304 is reached only after the access check.
• [x] test/tokens-etag.test.ts covers each of the above and fails without the change.

Files: src/http/api/tokens.ts, test/tokens-etag.test.ts. Risks: do not touch src/http/api.ts; the body stays byte-for-byte as it is.

Reviewed pull #9209 at its head: ticked The /api/v1/tokens route in src/http/api/tokens.ts answers 200 with a weak etag from weakEtag (src/http/etag.ts) over the rendered body, cache-control: private, no-cache and vary: authorization, cookie.; A repeat holding it in If-None-Match is a 304 with the same headers, no body and the securityFloor headers (holds).; The etag moves when a token is created, revoked, or its last-used time or client changes; two viewers who are shown different bodies never share an etag.; No session or account answer exactly as today, with no ETag, even with If-None-Match: *; the 304 is reached only after the access check.; test/tokens-etag.test.ts covers each of the above and fails without the change..