Description of problem:

Using `CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN: "true"`  with Gitlab provider refreshes the token and creates a new PAT secret everytime the workspaces is refreshed, without deleting the previous secret.

Workaround

NA

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

1.  Install 3.15 Devspaces and set `CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN: "true"` as per documentation: https://docs.redhat.com/en/documentation/red_hat_openshift_dev_spaces/3.15/html/administration_guide/configuring-devspaces#configuring-oauth-for-git-providers
2. Create Ouath for Gitlab and launch a new workspace. A PAT secret is created in user namespace
3. Restart the workspace, token is refreshed , a new secret is created, but the old PAT token secret still persists.

Actual results:

Old PAT token secret persists, after the token refresh with workspace restart

Expected results:

The old PAT token secret is replaced with the new one on token refresh.

Reproducibility (Always/Intermittent/Only Once):

Always

Acceptance criteria: 

Definition of Done:

Build Details:

Additional info (Such as Logs, Screenshots, etc):

 *