Enable protected secrets by default

[Furisto]

Description

Enable protected secrets by default. This is the follow up to #14083 on the web app side. Now that gen73 has been deployed we do not need to send the protected_secrets feature flag any more in order to enable protected secrets

Related Issue(s)

Fixes #13634

How to test

Release Notes

None

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

[werft-gitpod-dev-com]

started the job as gitpod-build-fo-protected-secrets-2.3 because the annotations in the pull request description changed
(with .werft/ from main)

[Furisto]

/werft run with-preview cert-issues=letsencrypt

👍 started the job as gitpod-build-fo-protected-secrets-2.17
(with .werft/ from main)

[easyCZ]

LGTM.

FYI, currently when this PR lands, the WebApp part will likely rollout sooner. This means you'll no longer be receiving the feature flag on the request. It looks like that's not a problem here as you've already handled the default on ws-manager. Just wanted to call that out.

[Furisto]

This means you'll no longer be receiving the feature flag on the request. It looks like that's not a problem here as you've already handled the default on ws-manager.

@easyCZ Yep, the changes for the workspace cluster were deployed with gen73 to ensure that we still use protected secrets