Solution Validation: Add CI job token and GAT to the `Access Token` menu

What's this issue all about? (Background and context)

Currently CI job token is in Settings -> CI/CD -> Token Access. CI job token is frequently confused with PAT. Having both of these in the same settings menu area would help clarify the two and reduce confusion. Moving CI job token will also help with #434607.

Additionally, we are curious if it makes sense to add Group Access Tokens for visibility in the same area.

What hypotheses and/or assumptions do you have?

CI job token and PAT/GAT are both types of token that grant access. As a result, users will find it more intuitive for them to be in the same Settings. This may lead to a need to rename the Setting itself from Access Tokens to something more generic, especially if there are other similar-natured tokens within GitLab.

What questions are you trying to answer?

Is CI job token categorized with PAT/GAT by our users? Is the experience more intuitive to access all 3 of these in the same area? Are there other permission concerns in categorizing these together?

What research methodology do you intend to use?

  • User interviews

What persona, persona segment, or customer type experiences the problem most acutely?

Individuals who frequently use Job Tokens, PATs, and GATs in their workflows:

What business decisions will be made based on this information?

This will determine if we should move CI job token's settings to Settings -> Access Tokens

What, if any, relevant prior research already exists?

Who will be leading the research?

@bonnie-tsang and @jocelynjane

What timescales do you have in mind for the research?

1-2 milestones to recruit, interview, and summarize the results for next steps.

Relevant links (problem validation issue, design issue, script, prototype, notes, etc.)

Edited by Bonnie Tsang