Obtain and persist Bitbucket personal access token as k8s secret

[skabashnyuk]

Is your task related to a problem? Please describe.

To be able to use Bitbucket personal access token during factory resolution #18386
and git operations we want to persist them as k8s secrets

Describe the solution you'd like

Obtain and persist Bitbucket personal access token as k8s secret

apiVersion: v1
kind: Secret
metadata:
  name: bitbucket-personal-access-token-secret
  labels:
    app.kubernetes.io/part-of: che.eclipse.org
    app.kubernetes.io/component: bitbucket-personal-access-token
  annotations:
    che.eclipse.org/expired-after: 12323423
    che.eclipse.org/che-userid: 7234090-45345234
    che.eclipse.org/bitbucket-userid: 34593094509
    che.eclipse.org/bitbucket-username: 'tshevchenko'
data:
  token: ZHNhZmFkZmFzZGZxMzRyMzRyMTM0

apiVersion: v1
kind: Secret
metadata:
  name: git-credentials-secret
  labels:
    app.kubernetes.io/part-of: che.eclipse.org
    app.kubernetes.io/component: workspace-secret
  annotations:
    che.eclipse.org/expired-after: 12323423  
    che.eclipse.org/che-userid: 7234090-45345234
    che.eclipse.org/automount-workspace-secret: 'true'
    che.eclipse.org/mount-path: /home/theia/.git-credentials
    che.eclipse.org/mount-as: file
    che.eclipse.org/git-credential: 'true'
    che.eclipse.org/bitbucket-personal-access-token-secret: 'bitbucket-personal-access-token-secret'
data:
  credentials: aHR0cHM6Ly91c2VyOnBhc3NAZXhhbXBsZS5jb20K

Describe alternatives you've considered

n/a

Additional context

#18385

[skabashnyuk]

In my "experimental code" #18726 I was to able determine the current Bitbucket user (that was quite a complicated thing because Bitbucket server has no API to figure out that) and obtain and persist server personal access code.

[skabashnyuk]

In c8772d2 changed

1. Git credential secret - changed name to [scm-user-name]-git-credentials-secret-[5 random]
2. Git credential secret - added che user id annotation
3. Personal token secret - changed name to personal-access-token-[5 random]
4. Personal token secret - added che.eclipse.org/scm-personal-access-token-id
5. Personal token secret - added che.eclipse.org/scm-personal-access-token-name
6. Bitbucket token - changed name to che-token--
7. Bitbucket token - changed name to che-token--
8. BitbucketPersonalAccessToken - added lastAuthenticated, ignoring default fields on decerialization.

Now secrets look like this: