Add a retry for tests creating access tokens

What does this MR do?

Fix for #285135 (closed)

I have noticed that when running QA tests against GDK (master or branches) they can often fail when creating the token.

The issue seems to be that the name is not entered. Thus the token is not created and the test being ran fails as it cannot find the created_access_token element (that does not exist due to no name)

This MR retries filling in the name.

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related to #285135 (closed)