Catch delete token error if namespace is not provisioned

[vinokurig]

What does this PR do?

Do not throw an error on Git Service revoke if the related oauth access token is not deleted.
Currently dashboard has a timer that controls che-server's namespace provision API request: If the namespace provision is executed another provision request will be ignored for 15 seconds:

che-dashboard/packages/dashboard-frontend/src/store/SanityCheck/index.ts

Lines 83 to 88 in 4b58763

	if (timeElapsed < timeToStale) {
	dispatch({
	type: Type.ABORT_BACKEND_CHECK,
	});
	return;
	}

This timer causes a side effect that activates the revoke a Git service button after an actual revoke is performed. With this PR we intercept the delete token error on such case and deactivating the revoke button.

What issues does this PR fix or reference?

Is it tested? How?

1. Setup GitHub oauth: https://eclipse.dev/che/docs/stable/administration-guide/configuring-oauth-2-for-github
2. Start a workspace from a GitHub repository, accept the GitHub token agreement.
3. Go to the dashboard Git Services tab and revoke the GitHub authorisation.
4. Quickly go to the Personal Access Tokens tab and then quickly switch back to the Git Services tab.
5. See: the GitHub still has an authorised state as the provision request was ignored and the related oauth token was not deleted.
6. Revoke the GitHub authorisation.
7. See: a notification about successful revoke appears and the authorisation status is changed to unauthorised.

Release Notes

Docs PR

[che-bot]

Click here to review and test in web IDE:

[github-actions]

Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-1046

kubectl patch command

kubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1046", name: che-dashboard}]}}]"

[ibuziuk]

please, take a look at the screencast since I'm not sure PR is addressing the issue I'm facing:

Screen.Recording.2024-01-19.at.13.45.50.mov

[github-actions]

Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-1046

kubectl patch command

kubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1046", name: che-dashboard}]}}]"

[olexii4]

@ibuziuk Could you recheck these changes? I fixed a bug and added tests.

2024-01-24.04.00.07.mov

[github-actions]

Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-1046

kubectl patch command

kubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1046", name: che-dashboard}]}}]"

[codecov]

Codecov Report

Attention: 11 lines in your changes are missing coverage. Please review.

Comparison is base (fb4e0c6) 88.24% compared to head (c00581e) 88.28%.
Report is 3 commits behind head on main.

Files	Patch %	Lines
...shboard-frontend/src/store/GitOauthConfig/index.ts	33.33%	8 Missing ⚠️
...ontend/src/store/Workspaces/devWorkspaces/index.ts	86.36%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1046      +/-   ##
==========================================
+ Coverage   88.24%   88.28%   +0.03%     
==========================================
  Files         389      390       +1     
  Lines       39845    39984     +139     
  Branches     2650     2666      +16     
==========================================
+ Hits        35163    35299     +136     
- Misses       4656     4659       +3     
  Partials       26       26              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ibuziuk, olexii4, vinokurig

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vinokurig]

Needs another approach.