Set API-key authority, counter, and status semantics

[salasebas]

Question

For the v1.6.24 API-key deltas covering config selection, 429 status, authoritative sessions, stale-write protection, concurrent deletion, remaining-use counters, rate limits, secondary-only best-effort behavior, organization authorization, and trusted client IPs, what exact RustAuth contract should ship? Decide any compatibility warning or public storage capability requirements and the required synchronized tests.