Set explicit AUTH TOKEN for r/w access v2.0 API

__Proposal:__
Allow setting explicit TOKEN for user via CLI: `influx auth create --force-auth-token {token}`

__Current behavior:__
`influx auth create` Generates new random access token every time.
Obtaining a token needs user input.

__Desired behavior:__
Add a flag to pass desired TOKEN when creating auth token like eq: `--force-auth-token`
Behavior similar to `influx v1 auth create` where user can pass explicit `--password` for access

__Alternatives considered:__
Alternatively allow to change existing TOKEN to other, provided in CLI command

__Use case:__
- When automating new instance of Influx, telegraf, grafana etc. to automatically configure with proper r/w user + token
- When using Influx HA eg: Bitnami Kubernetes HELM chart, Setting AUTH TOKEN is only possible for ADMIN user, when using 2+ Influx instances behind a service or LoadBallancer, I would like to finely granulate r/w access. BUT every Influx instance creates its own access token thus using an ADMIN token is the only way, disabling AUTH mechanism for influx entirely, as read/write is only possible for admin user.

Start at the `influx auth create --force-auth-token` CLI entry point and trace the current random-token creation behavior. Compare it with `influx v1 auth create --password` and determine how an explicitly supplied token should be handled across the API. Done means automated creation can provide a chosen token while preserving the requested read/write access behavior.

Written by the indexing model from the issue text.