[ws-manager-bridge] Support forced cluster dereg

[csweichel]

Description

This PR adds support for forced workspace cluster deregistration.
When de-registering a cluster, ws-manager-bridge checks if there are still any workspaces which belong to this cluster and are marked as running. If we removed the cluster in this case, those instances would never again receive a status update - also the reconciliation in ws-manager-bridge would no longer act on those workspaces (the cluster is gone after all, what should we reconcile with).

With the newly added --force flag on gpctl, we can override this safety mechanism in exceptional cases, e.g. when introducing new workspace cluster types.

How to test

1. Register the same ws-manager as dynamic cluster and give it a very high score
2. Start a workspace on that cluster
3. Deregister the newly added cluster - should not work without --force, but should work with it.

Release Notes

[gpctl] Support forceful cluster de-registration

[csweichel]

/approve no-issue

[aledbf]

/lgtm

[roboquat]

LGTM label has been added.

Git tree hash: cc1fc47b4fd6f3698a4cf56f2764cbf94e4dee5d

[csweichel]

/werft run

👍 started the job as gitpod-build-cw-cluster-force-dereg.1

[codecov]

Codecov Report

Merging #6682 (822cf4f) into main (43f041d) will decrease coverage by 1.72%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##            main   #6682      +/-   ##
========================================
- Coverage   7.89%   6.16%   -1.73%     
========================================
  Files         14      12       -2     
  Lines       1254    1086     -168     
========================================
- Hits          99      67      -32     
+ Misses      1152    1018     -134     
+ Partials       3       1       -2     

Flag	Coverage Δ
components-local-app-app-linux-amd64	?
components-local-app-app-linux-arm64	?
components-local-app-app-windows-386	?
components-local-app-app-windows-amd64	?
components-local-app-app-windows-arm64	?
installer-raw-app	6.16% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
components/local-app/pkg/auth/pkce.go
components/local-app/pkg/auth/auth.go

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 43f041d...822cf4f. Read the comment docs.

[geropl]

👍 for the PR. We just need to be aware that leaving dangling workspaces around currently breaks UX for people that started those (bc they might run into an unresolvable "max parallel workspaces" situation). We had this incident end of last week with a temporary k3-eu102 cluster, for instance.

So fine with merging this as long as we:

• are careful when using it
• until we have some kind of garbage collector for "workspace that are not stopped but whose ws cluster is not available anymore (for some time)" (issue: [ws-manager-bridge] Garbage-collect workspace instances whose workspace clusters are not available anymore #6770)

[geropl]

LGTM , but keep #6682 (comment) in mind.

[roboquat]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aledbf, csweichel, geropl

Associated issue requirement bypassed by: csweichel

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

The pull request process is described here

Needs approval from an approver in each of these files:

• components/ws-manager-bridge/OWNERS [geropl]
• components/ws-manager-bridge-api/OWNERS [csweichel,geropl]
• dev/gpctl/OWNERS [aledbf,csweichel]

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