Description of problem:

This is observed for Azure DevOps/Bitbucket.org/GitHub.com git providers when using 'CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN' property.
Every start a workspace creates new token, but an old is not removed (there is known issue). When their number exceeds 5, run workspace is fail and more of that an <user>-devspaces becomes unavailable, is not possible go to Dashbord.

See screenshots:

Workaround
N/A

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

• configure OAuth in a git provider

Steps to Reproduce

• deploy DS 3.16.0
• add the property 'CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN' to CheCluster
• run workspace using factory of a git provider
• try stop/start workspace more than 5 times

Actual results:

• workspace does not run
• Dashbord is not available

Expected results:

• workspace should run
• Dashboard is available

Reproducibility (Always/Intermittent/Only Once):

Acceptance criteria: 

Definition of Done:

Build Details:

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

 *