Increase tests personal access token expiry

What does this MR do?

This increases the personal access token expiration by 1 day so that people in certain timezones can run the tests locally after a certain time.

When I run the tests on my GDK after 8pm (EDT), the token is immediately expired, giving this error:

...using the API failed (401) with `{"error":"invalid_token","error_description":"Token is expired. You can either do re-authorization or token refresh."}`.

If I increase the expiry to 3, the token is created with an expiration date of today's date + 1 and the tests run.

Screenshots

Date is entered as today's date + 2:

Once selected, date changes to today's date + 1:

Token says it's created but it's already expired:

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