[db] DBPrebuiltWorkspace: Add index ind_creationTime

[geropl]

Description

Summary generated by Copilot

🤖 Generated by Copilot at 4a35e53

This pull request adds an index on the creationTime column of the DBPrebuiltWorkspace table to improve the performance of prebuild queries. It also adds a migration file to create or drop the index in the database schema.

Related Issue(s)

Fixes EXP-710

How to test

Documentation

Preview status

Gitpod was successfully deployed to your preview environment.

• 🏷️ Name - gpl-710-count-pws
• 🔗 URL - gpl-710-count-pws.preview.gitpod-dev.com/workspaces.
• 📚 Documentation - See our internal documentation for information on how to interact with your preview environment.
• 📦 Version - gpl-710-count-pws-gha.17779
• 🗒️ 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
• 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

[mustard-mh]

LGTM

But I'm curious about why we should write migration down for index adding?

[geropl]

But I'm curious about why we should write migration down for index adding?

IMO in general we should go with the habbit of adding down implementations. But you are right, we are not making proper use of them, yet. 👍

[geropl]

/unhold