Increase JetBrains IDE process priority

[iQQBot]

Description

This PR increases JetBrains IDE process priority (niceness -10)

Related Issue(s)

Fixes ENT-158

How to test

1. start a workspace with any JetBrains IDE
2. using ps -eo pid,nice,args --sort=nice | awk '$2 != 0' you will see Jetbrains IDE process is -10 (This may take some time)

Documentation

Preview status

Gitpod was successfully deployed to your preview environment.

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

[meysholdt]

This is great, thank you for this PR.

nit: When testing, let's please make sure that processes started via the IDE's Terminal do not get niceness -10.
For example, when running gradle from the terminal, it should not get -10, because that might render the workspace unresponsive.

[iQQBot]

nit: When testing, let's please make sure that processes started via the IDE's Terminal do not get niceness -10. For example, when running gradle from the terminal, it should not get -10, because that might render the workspace unresponsive.

In terms of implementation, it is impossible to avoid this. They will always first get -10, but they will be adjusted to 0 at a later time. @meysholdt

[iQQBot]

The child process always gets the same niceness as the parent process, which cannot be changed and can only be modified after the process starts.

[meysholdt]

In terms of implementation, it is impossible to avoid this. They will always first get -10, but they will be adjusted to 0 at a later time.

I think if the "adjustment" happens fast enough (withing seconds), this should be all we need. let's try.

[iQQBot]

/unhold