Increase default OIDC token expiration - migration from PAT introduces unintended side-effects

[JackPGreen]

I've migrated workflows from using login-action with a secret token, to use OIDC - this works well, and is very welcomed.

However, this also introduces a non-obvious behaviour:

• previously, the token was long-lived, the subsequent steps can interact with docker with authentication (pull, push etc)
• now, the token is short-lived (5 minutes by default), which means subsequent steps might not be able to interact with Docker if execution takes too long

Imagine a workflow that exists to build/push some non-trivial image - e.g. downloads a file, installs some packages etc:

1. login-action via OIDC
2. build-push-action builds and pushes image in a single step - except this will fail, because the token will have expired during the build of the image

The error message will merely say unauthorized: incorrect username or password which does not immediately point to a credential expiration issue.

Similarly, even with a trivial image in a complex workflow you can run into the same issue:

1. login-action via OIDC
2. build-push-action builds and pushes a simple image
3. subsequent workflow actions that take >5 minutes (perhaps tests)
4. any subsequent Dockerhub action - even pulling a public image - will now fail as the credentials have expired

I think that for oidc-action, 5 minutes makes sense, but maybe for login-action it should be higher - or alternatively, the documentation could be improved to stress the (implicit) short-lived nature of the authentication.