Changelog: fixed

Rather than repeatedly disabling it, just allow it in scripts and
configuration files.

- Remove pdf from webpack.vendor.config
- Support both versions of pdfjs in webpack.constants.js
- Pull pdfjs consts into its own file
- Fix tests

* Update path resolve for `jh_else_ee` in vite/webpck.
* Update eslint for JiHu.

- import worker manually
- only apply when using Vite
- make check in vite config

Changelog: changed

The encompasses a few changes:

1. extend the `universal_stylesheet_link_tag` and
   `universal_path_to_stylesheet` to serve styles directlt from `vite`.
1. use `vite`'s native SCSS feature. This needs a lot of config changes.
1. Use alias for @gitlab fonts: Otherwise we get files under
   `public/assets/@gitlab`. And who knows how well reverse proxies
   and such would handle built assets that have an at in the URL.

Fixes the __open_in_editor url so files can be directly opened
in the Code editor when using Vue Devtools.

Changelog: fixed

Vite Plugins have the `config` hook and if the config hook returns a
partial config, they are deeply merged.

This means that the plugins themselves can define a partial config:
- https://vitejs.dev/guide/api-plugin#config

Yes, and that is the last one for now!

So you are really reading these

And rename it to AutoStopPlugin, because that's what it is doing!

Because this makes our config a little more readable.

This removes the `tailwind_all_the_way` feature flag. We had the flag
enabled long enough in production to catch and fix a few regressions. We
are now ready to remove the flag and rely on a single Tailwind config
which will allow us to resume the migrations.

Changelog: added

We have the controller `profiles/keys` with the action `show`, so it
tries to load: `pages.profiles.keys.show.js` which doesn't exist. The
following entry points do exist:

   pages/profiles/keys/show/index.js <== does not exist
   pages/profiles/keys/index.js <== does exist
   pages/profiles/index.js <== does exist

So, it should have tried loading the other two, but didn't. By moving
the "backtracking" logic to the backend, we can try loading all of those
virtual entry points.

Older GDKs previously did not have Vite HMR configured properly, but
now they do. Drop the fallback behavior so that HMR can be disabled
properly.

We have a few dependencies for which we copy static assets to
`public/assets/webpack`: WebIDE, Source Graph and the PDF viewer.

In webpack we use the `copy-webpack-plugin` for this. It basically takes
an array of files/directories and copies them to
`public/assets/webpack`.

In this commit we move the definition for this to `webpack.constants.js`
and import it to `vite.config.js`. Given our config for the
`copy-webpack-plugin` is rather limited (only absolute paths, no globs),
we can re-implement a rather smallish scope of the plugin for vite.

Basic setup for compiling Tailwind CSS utilities

We want to watch when hot module reloading is _enabled_.

We run tests in CI with `vite` (`e2e:test-on-gdk`). When these run in
CI, we do not need to watch our CSS assets, because the CSS is not going
to be changed during the run of the pipeline. Therefore we just make the
CSS compiler respect the hot module reloading setting.

By moving most of the CSS compilation to a lib file, we will be able to
reuse it more easily in some other scripts.

Disable hot reloading

Add explicit message for content expansion wait

Explicitly disable watcher when hot reload is disabled

Remove watchers increase

Do not run load balancer tests automatically

Add back ff network per build option

Remove hostname update

Add ci specific log path

By setting a different client port we can make the nginx reverse
proxy work properly. The corresponding GDK was merged here:
https://gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/3501

We also now start vite on the correct host and we load the
settings directly from `config/vite.gdk.json`.




This is easier than loading it via the environment. We are not requiring
the JSON with an `import` because loading it via readFile is a little
more future proof for ESM.

This makes sure we only watch relevant files and avoids the
"number of file watchers reached" issues seen on Linux systems.

With a custom function we can stop vite from starting recursing down
the whole root folder. This makes the whole thing way more efficient.

We use config/vite.json to define additional paths we want watched.

Highlights all HLJS languages with highlight worker

We sometimes prune our complete `node_modules` folder, so by moving our
cache dir to `tmp/cache` (where `jest`, `webpack`, `babel` reside
already), we can prevent removal of our cache folder.

This should improve startup times of vite as well, after branch
switches.