The default devfile is resolved from private bitbucket repo after access token is revoked

[sleshchenko]

Describe the bug

The default devfile is resolved from private bitbucket repo after access token is revoked.

Che version

• latest
• nightly
• other: please specify

Steps to reproduce

0. Prereq: Che with bitbucket oauth configured.
1. Open a factory which points to private bitbucket repo.
2. Authentication in the bitbucket after redirect.
3. Check that the right devfile is used for workspace creation.
   my case:

apiVersion: 1.0.0
metadata:
  generateName: wksp-

4. Go to bitbucket and revoke access to the generated token.
5. Retry accept the same factory.
   Check that workspace is created but instead of resolved devfile, the default generated is used, like:

apiVersion: 1.0.0
metadata:
  name: test-repo7hbgl
projects:
  - name: test-repo
    source:
      location: 'https://bitbucket-bitbucket.apps.cluster-460f.460f.sandbox1282.opentlc.com/scm/test/test-repo.git'
      type: git

Expected behavior

User is ask to re-authenticate since Che owned token is already revoked.

Runtime

• kubernetes (include output of kubectl version)
• Openshift (include output of oc version)
• minikube (include output of minikube version and kubectl version)
• minishift (include output of minishift version and oc version)
• docker-desktop + K8S (include output of docker version and kubectl version)
• other: (please specify)

Screenshots

Screenshots

Installation method

• chectl
  • provide a full command that was used to deploy Eclipse Che (including the output)
  • provide an output of chectl version command
• OperatorHub
• I don't know

Environment

• my computer
  • Windows
  • Linux
  • macOS
• Cloud
  • Amazon
  • Azure
  • GCE
  • other (please specify)
• other: please specify

Eclipse Che Logs

Additional context

Bitbucket epic - #18385