Update useLatestVersion in autostart options when user pref updaetd

[selfcontained]

Description

When a user changes their ide preference to either use latest version, or stable, we update any records we have under user.additionalData.workspaceAutostartOptions and update the ideSettings.useLatestVersion` to whatever they changed their preference to. This helps fix an issue where users can't change from latest/stable after starting a workspace on a repo.

Summary generated by Copilot

🤖[deprecated] Generated by Copilot at fe41d7c

Update autostart options for workspaces based on user's IDE choice in SelectIDE.tsx. Add TODO comment to refactor user object mutation.

Issues

Fixes EXP-865

How to test

• Make sure your user prefs are set to NOT use the latest version of the ide
• Start a workspace on a repo (should not be the latest version).
• Change your user ide pref to use the latest version
• Go to the create workspace page and select the same repo.
• It should now be using Latest for the IDE
• Turn the use latest pref back off and verify if you try to create a workspace for that same repo it isn't using the latest version.
• You can also do the same steps testing autostart by manually constructing the URL for your repo, and adding ?autostart=true to the url (before the #<repo-url> hash)

Documentation

Preview status

Gitpod was successfully deployed to your preview environment.

• 🏷️ Name - brad-use-lf2431f1eca
• 🔗 URL - brad-use-lf2431f1eca.preview.gitpod-dev.com/workspaces.
• 📚 Documentation - See our internal documentation for information on how to interact with your preview environment.
• 📦 Version - brad-use-latest-autostart-options-gha.21203
• 🗒️ Logs - GCP Logs Explorer

Build Options

Build

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish

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

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• /werft preemptible
  Saves cost. Untick this only if you're really sure you need a non-preemtible machine.
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

/hold

[akosyakov]

/gh run recreate-vm=true

[mustard-mh]

[not-blocking] Will it be better to not store version (latest, stable) in autostart option but always get the current editor settings?

[mustard-mh]

Code LGTM.

Tested with latest enable / disable / enable, works as promised. Validate by latest editor warning

[selfcontained]

[not-blocking] Will it be better to not store version (latest, stable) in autostart option but always get the current editor settings?

That's an interesting idea 🤔

I'm going to go ahead w/ this approach for now to get the bug addressed, and not totally sure what side-effects that approach would have yet. When we revisit this page we should consider an approach like that though, as it could remove a layer of settings potentially in the logic.

[selfcontained]

/unhold