New personal access token UI no longer supports pre-filled token query parameters

Summary

It looks like pre-filled access token scopes and names are no longer working after Swap out personal access tokens UI (!189817 - merged) was deployed.

A contributor at for the bundled GitLab JetBrains plugin reached out to ask if this was expected but looks like a regression introduced by recent changes to the personal access tokens page.

Steps to reproduce

  1. Try to follow the steps in https://docs.gitlab.com/user/profile/personal_access_tokens/#prefill-personal-access-token-name-and-scopes
  2. Notice that you aren't taken to a page with the new access token form being pre-filled with the correct options.

Example Project

What is the current bug behavior?

Pre-filled scopes/name are cleared on page load and the form is not opened.

What is the expected correct behavior?

Previous pre-filled scopes and names query parameters being included trigger the form being expanded and pre-populated on page load.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.