Misleading parameters in get-access-token

[systemstart]

Description

The subcommand get-access-token offers a parameter --project-id.

One might get the idea the resulting token is valid for that project only, which is not the case since --project-id (and --region for example) is not used.

Steps to reproduce

1. Run TOKEN=$(stackit auth get-access-token --project-id=$PROJECT_ID)
2. Run curl -H "Authorization: Bearer $TOKEN" https://ske.api.stackit.cloud/v2/projects/$OTHER_PROJECT_ID/regions/eu01/clusters/$SOME_CLUSTER_ID

Actual behavior

The --project-id parameter has no effect on the resulting token.

Expected behavior

I would either assume

• the token to be only valid for the project ID provided to get-access-token
• or not showing the parameter in get-access-token --help.

Environment

• OS: Linux
• Version of STACKIT CLI (see stackit --version): v0.42.0