[gitpod-code] gp rebuild hints experiment

[akosyakov]

Description

This PR adds an experiment to improve discoverability of gp rebuild feature in VS Code interface:

• via a notification on save of .gitpod.yml or Dockerfile
• UI actions in code lenses, editor context and inline menus

gitpod-code commit on master

Related Issue(s)

Fixes #16299

How to test

• Start a workspace and verify that you don't have new features.
  • For fast startup you can use this context: https://github.com/akosyakov/parcel-demo/tree/tiny
• Enable gitpod_experiments_rebuildHints feature flag for your user in Configcat.
• Reload the window and verify that you have new features now.

Release Notes

NONE

Documentation

Build Options:

• /werft with-github-actions
  Experimental feature to run the build with GitHub Actions (and not in Werft).
• leeway-no-cache
  leeway-target=components:all
• /werft no-test
  Run Leeway with --dont-test

Publish Options

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer Options

• with-ee-license
• with-slow-database
• with-dedicated-emulation
• with-ws-manager-mk2
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment Options:

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft analytics=segment
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• /werft with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

[werft-gitpod-dev-com]

started the job as gitpod-build-ak-code-validate.1 because the annotations in the pull request description changed
(with .werft/ from main)

[akosyakov]

/werft run

👍 started the job as gitpod-build-ak-code-validate.2
(with .werft/ from main)

[akosyakov]

/werft run with-preview with-gce-vm

👍 started the job as gitpod-build-ak-code-validate.3
(with .werft/ from main)

[akosyakov]

/werft run with-clean-slate-deployment=true

👍 started the job as gitpod-build-ak-code-validate.6
(with .werft/ from main)

[filiptronicek]

/hold

[filiptronicek]

Thanks for the changes, everything looks like working well -- I get both the notifications on save and the context menu options.

There's just one small bug that happens when you create a .gitpod.yml not in the project root - you can still see all the options, although if you decide to act on them and Validate, it will use the root .gitpod.yml, which users may not expect. I think we should disable context menus for non-root .gitpod.ymls. Let's talk about this async if even

[filiptronicek]

/unhold

[akosyakov]

There's just one small bug that happens when you create a .gitpod.yml not in the project root - you can still see all the options, although if you decide to act on them and Validate, it will use the root .gitpod.yml, which users may not expect. I think we should disable context menus for non-root .gitpod.ymls. Let's talk about this async if even

We should provide --workspace-folder then, but I won't do anything for now.