I am bumping the required JAVA SDK to 11 since it simplifies its usage
which results in improved maintanability. It also eliminates the need to
use bootclasspath.

- Merge VTK_JAVA_TARGET_VERSION and VTK_JAVA_SOURCE_VERSION to
  VTK_JAVA_RELEASE_VERSION.
- RENAME VTK_JAVA_INSTALL to VTK_JAVA_BUILD_MAVEN_PKG.
- Update Java build instructions

Co-authored-by: Ben Boeckel <ben.boeckel@kitware.com>

(cherry picked from commit 45b5fbb3)

Historically, `needs` specifies the jobs which need to complete
successfully and `dependencies` specifies the jobs which provide
artifacts which should be used. Modern GitLab discourages using both as
`needs` now supports an `artifacts` key to say "depend on but do not use
artifacts", so remove `dependencies` and use `needs:artifacts` where
necessary.

See: https://docs.gitlab.com/ee/ci/yaml/#needsartifacts

Historically, `needs` specifies the jobs which need to complete
successfully and `dependencies` specifies the jobs which provide
artifacts which should be used. Modern GitLab discourages using both as
`needs` now supports an `artifacts` key to say "depend on but do not use
artifacts", so remove `dependencies` and use `needs:artifacts` where
necessary.

See: https://docs.gitlab.com/ee/ci/yaml/#needsartifacts

Historically, `needs` specifies the jobs which need to complete
successfully and `dependencies` specifies the jobs which provide
artifacts which should be used. Modern GitLab discourages using both as
`needs` now supports an `artifacts` key to say "depend on but do not use
artifacts", so remove `dependencies` and use `needs:artifacts` where
necessary.

See: https://docs.gitlab.com/ee/ci/yaml/#needsartifacts

- Since the standard linux tester tags do not
  inject GPU into the docker container, the browser tended
  to use the mesa driver and chrome fell back to an unstable
  software implementation of webgpu/webgl2 which lead to a
  very high rate of failures.
- This commit entirely removes wasm testing in linux because
  there is no real requirement to run the wasm tests in linux
  browsers right now. On top of that, there don't seem to be
  that many linux runners which inject the GPU into a container using
  nvidia-container-toolkit. Theoretically, linux_cuda_tester_tags could work,
  but there's not a sufficient number of runners with that tag.

The jobs should also not run for merge requests.

This should reduce the pressure merges put onto the CI system.

See: #19507

Surveying the CI machines shows that `large-memory` is not actually more
memory per-core in pracitice as it was intended to be. Remove the tag so
that it can eventually be phased out completely.

- The `vtkEGLRenderWindow` class is always built in linux.

- The `vtkOSOpenGLRenderWindow` class is always built

Jaswant Panchumarti (Kitware) authored 7 months ago and Jaswant Panchumarti (Kitware) committed 7 months ago

- these are no longer required because running vtk unit tests in browser
doesn't need threads anymore
- running tests in browsers with threads is unstable right now because
of instabilities due to webworker oversubscription
- https://github.com/emscripten-core/emscripten/issues/12223

- run tests only for threaded variants because wasm testing needs threads.
- package and upload both threaded and non-threaded tarballs.

- Use cmake script to download node, the shell script was removed.
- Merge the wasm upload job and use `WASM_WORDSIZE` env var to distinguish between 32/64 bit

They can be made available by setting the `RUN_OLD_PYTHON_WHEELS`
pipeline variable to `true`.

To make sure that instantiation problems are caught.

- This partially reverts commit 9d683a6d.
- Wasm jobs in Windows are brought back by testing the Linux artifacts.
- The build name has been updated with an `_ext_vtk` to indicate
  external testing
- wasm64-windows job is disabled until wasm32-windows shows some sign of stability.

- since chrome is no longer necessary or used in the build stage,
  this commit removes `chrome` from linux build job names and the cmake
  configuration file names.
- adds an `ext_vtk` suffix for the wasm(32|64)-emscripten-linux-chrome:test-ext
  jobs.

- address vtk/vtk#19375
- frees up windows resources for the moment
- eventually, will bring back wasm testing on windows to fix vtk/vtk#19375

Use a variable from the configuration part to distinguish the wordsize
of the target.

Script blocks should just be command sequences, not specify the image to
use.