Tag VS Code Insiders versions accordingly

[filiptronicek]

Description

When building VS Code Browser images, take a look at whether it's a stable or insiders release and if the latter, tag it as such (e.g. 1.74.0-insider). Previously, we did not take quality into account.

Related Issue(s)

Fixes #

How to test

Release Notes

Documentation

Werft options:

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

[roboquat]

@filiptronicek: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[werft-gitpod-dev-com]

started the job as gitpod-build-ft-tag-vscode-insiders-with-corresponding-suf.1 because the annotations in the pull request description changed
(with .werft/ from main)

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.