Cli admin create user --access-token option should also require a --scopes option

[akarasulu]

Feature Description

The token created via gitea admin create user --access-token is effectively useless without providing some minimal scope options. The generated scopeless access token, as expected, always results in a 403 with "token does not have required scope" messages via REST API. There's no way to change the scope afterward either.

Without the ability to provide scopes the --access-token features is completely useless.

Screenshots

This shows the current token scopes (none) as the feature stands without having the option to specify scopes. Another option is from my comment below where all powers are granted to the access token generated for admins from the CLI.

[delvh]

That strongly depends on #24767 first…

[akarasulu]

That strongly depends on #24767 first…

From a DevOps point of view, the token created with an admin user (via CLI) should have all scopes automatically set when creating the token, including the ability to delete this "all-powers" token after the automated configuration completes.