[server] Restart PVC workspace from latest valid backup

[geropl]

Description

Related Issue(s)

Fixes #14030

How to test

1. open a workspace on this PR
2. make sure user_pvc is enabled for your user in ConfigCat
   1. after changing the rule, kubectl rollout restart deployment/server
3. login
4. start a workspace
5. check the workspace pod, and verify that the label gitpod.io/pvcFeature: "true" is present ✔️
6. stop the workspace
7. start and stop that workspace another time
8. manipulate the DB:
   1. Find the instances of your wrokspacId: select id, creationTime, status from d_b_workspace_instance WHERE workspaceId = ' ... ';
   2. Set the latest instance to failed; UPDATE d_b_workspace_instance SET status = JSON_SET(status, "$.conditions.failed", 'test') WHERE id = ' ... ';
9. Start your workspace again, and see how it work ✔️

Release Notes

NONE

Documentation

Werft options:

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-integration-tests=all
  Valid options are all, workspace, webapp, ide

[werft-gitpod-dev-com]

started the job as gitpod-build-gpl-14030-pvc.2 because the annotations in the pull request description changed
(with .werft/ from main)

[kylos101]

👋 @geropl when testing, I recommend this at least: /werft run with-integration-tests=workspace with-large-vm=true

[geropl]

I recommend this at least: /werft run with-integration-tests=workspace with-large-vm=true

Hey @kylos101 , thx for the pointer!
Can you explain why those'd help? 🤔

1. this should not affect any workspace integration tests
2. what does with-large-vm do? :-o

[kylos101]

Howdy @geropl ,

this should not affect any workspace integration tests

Good point! 🤦

what does with-large-vm do? :-o

This helps tests "run faster", sometimes they can timeout, by giving the preview environment more resources.

[jankeromnes]

when testing, I recommend this at least: /werft run with-integration-tests=workspace with-large-vm=true

FYI, it could help to put these options at the bottom of the PR description, so that every build of this PR gets them. 👍

[jankeromnes]

FYI, I tested this PR with various scenarii that failed in the context of Gitpod's PVC prebuilds / #13991 :

• incremental prebuilds
• same prebuild different branch
• opening prebuilds directly

(I have no idea if my workspaces/prebuilds were actually using PVC, but) doing these things worked perfectly. 🙌

[geropl]

(I have no idea if my workspaces/prebuilds were actually using PVC

@jankeromnes see description at the top on how to configure and check.

[sagor999]

LGTM