Token rotation and management scenarios

## Use the CLI or API to manage tokens for InfluxDB

Document best practices for token lifecycle management within and across InfluxDB editions

- Token issuance, revocation, and rotation
- Edge data and aggregation scenarios
- Within and across editions (on-prem <> edge <> cloud)
- Should we delete the authorization when we expire the tokens or mark them as Inactive and the deletion is done by InfluxDB management?

### Example scenarios

> In order to rotate the token. you may want to:
a) generate the new token with the appropriate permissions
b) begin the distribute the token to the various servers….which takes time. This means that BOTH tokens are active while this occurs.
c) when you believe that the token has been distributed to all 100 servers….disable/deactivate the original token.
d) it is possible that some servers didn’t get their token rotated successfully…so you may want to re-activate the original token while you investigate. (i.e. running a count() returns less than 100 when you disabled the original token….you figure out which servers dropped out…and investigate. Perhaps a server remains offline, etc.)
e) once you’ve confirmed everything is working….delete the old token.

### Future enhancements

- Database user management?

Start with the CLI and API token-management entry points, then compare token lifecycle behavior across InfluxDB on-prem, edge, and cloud editions. Document issuance, overlapping rotation, deactivation, reactivation, revocation, and deletion guidance, including the 100-server distribution scenario and the unresolved authorization question.

Written by the indexing model from the issue text.