[server] enhanced mocha setups

[svenefftinge]

Description

Changes the mocah setup in server component:

• run generated JS instead using very slow ts-node. (a bit more inconvenient as we have to rebuild/watch)
• working mocha extension in VS Code
• remove the launch configs (because the test explorer works better)

Summary generated by Copilot

🤖 Generated by Copilot at 56159f4

This pull request improves the testing setup for the server component, by aligning the database configuration with the test environment, using the compiled JavaScript files instead of the TypeScript files, and adding the hbenl.vscode-test-explorer extension to run and debug tests from VS Code in Gitpod.

Related Issue(s)

Fixes #

How to test

Documentation

Preview status

gitpod:summary

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

[akosyakov]

fine with me if it works, I remember we went similar way with Theia at some point because of differences running with ts-node or without

Not sure where we should document though testing flow that one HAS to recompile before running tests.

[github-actions]

⚠️ Hey reviewer! BE CAREFUL ⚠️
Review the code before opening in your Gitpod. .gitpod.yml was changed and it might be harmful.

[svenefftinge]

/unhold