Revisit tests that force create new PATs for default user to see if `GITLAB_QA_ACCESS_TOKEN` can be used

We had an incident in production due to large number of tokens for gitlab-qa user. Since we provide GITLAB_QA_ACCESS_TOKEN on staging and production, ideally we should need to create new tokens for the default user (with username set with GITLAB_USERNAME).

This issue is to revisit tests that explicitly create PATs with Resource::PersonalAccessToken.fabricate! for the default user to see if GITLAB_QA_ACCESS_TOKEN can be used if provided.