As docs pages get moved around or deleted, docs links that we display in
the product might become outdated without us noticing.
This adds an ESLint rule that ensures `helpPagePath` always points to
files and anchors that still exist.
In future iterations, we should add a similar rule to check usages of
the `HelpPageLink` Vue component, and a Rubocop rule for the backend
`help_page_path` helper.

- This will help us use workerIdleMemoryLimit
- https://gitlab.com/gitlab-org/gitlab/-/merge_requests/150196#note_1873162716
- Update snapshots with `yarn jest -u`
- Patch jest-mock to fix issues introduced with
  [this change][1]. See also [this note][2].
- We have to unset prettierPath because jest29
  doesn't work with prettier 3. This should be fixed
  in jest30. See [this relevant issue][3].
- We have to fix nwsapi because there's a bug that
  fails on certain query selectors. See
  [this upstream issue][4].
- We have to fix problematic `expect.objectContaining(null)`
  references which now throws an error.
- We're running into some overflow issues with recursive
  objects in `toMatchObject`. We need to update
  these references to `toEqual`. This looks like a
  known [Jest issue][5].
- Run dedupe on yarn.lock

[1]: https://github.com/jestjs/jest/pull/13503
[2]: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/151046#note_1986543058
[3]: https://jestjs.io/docs/configuration/#prettierpath-string
[4]: https://github.com/dperini/nwsapi/issues/114
[5]: https://github.com/jestjs/jest/issues/14734

Changelog: changed

Upgrades the gitlab-vscode-extension from v4.9.0 to v4.14.1

Changelog: changed

This reverts commit 0ca136e8, reversing
changes made to 243e40a5.

- See GitLab Workflow Extension CHANGELOG from v4.9.0 to v4.13.0
- https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/blob/main/CHANGELOG.md

Changelog: fix

Merge branch 'security-patch-web-ide-xss' into 'master'

See merge request gitlab-org/security/gitlab!4052

Changelog: security

Merge branch 'security-patch-web-ide-xss' into 'master'

See merge request gitlab-org/security/gitlab!4052

Changelog: security

Apparently we hit a very unlikely case that lead to our builds to be
unstable:

1. The `@vue/compiler` uses a small LRU cache with the latest 100 vue
   files it parsed.
2. It uses a `hash(filename + source + constant)` for the key of the
   cache. The hashing function has 2^32 different outcomes

With our code base we have a pure chance of a hash collision of 1.3 per
thousand. This collision happens with the two files at this commit:
850d6792

- app/assets/javascripts/work_items/components/work_item_state_badge.vue
- app/assets/javascripts/profile/components/user_achievements.vue

Now two more conditions needed to be fulfilled for it to become
problematic:

1. The two files needed to be parsed within a short period, otherwise
   the collision in the LRU cache would have been avoided. This explains
   why not every job was failing.
2. In order for the jobs to fail, the colliding files needed to use
   relative imports. If `work_item_state_badge.vue` accidentally loaded
   the content of `user_achievements.vue`, the relative import
   `./graphql/get_user_achievements.query.graphql` didn't exist. Vice
   versa if `user_achievements.vue` loaded the wrong contents, the
   relative import `../constants` didn't exist.

If neither of the colliding files would had relative imports, the
components might have been swapped silently, leading to potentially
undetected runtime errors.

We mitigate this issue by patching the hashing of the key to be:
`hash(a) + hash(b) + hash(c) + hash(d)` rather than `hash(a+b+c)`. This
decreases the likelyhood of collisions from `1.3 * 10^-3` to
`2.3 * 10^-9`, making it 570000 times less likely to hit a collision.

We probably should follow this up with an upstream contribution, so that
other large vue projects are not hit by this.

The updated version of the package actually abstracted things nicely,
but I don't think we should import `vue/compiler-sfc` given that we also
patch `@vue/compiler-sfc` ourselves.

Changelog: changed

This partially reverts merge request
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/131712 which
upgraded vue-apollo. The upgrade of vue-apollo was causing GraphQL
subscriptions to automatically restart which is causing increased Puma
CPU saturation as well as increased log messages. We do keep a fix of
vue-apollo that allows using props directly in vue provide by adding
a patch.

Changelog: fixed

This fixes a warning from patch-package about an old patch version.

This is a follow up to
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/132044.

* multiple minor fixes

* properly gather props/model from mixins
* mimic stub tag naming from @vue/test-utils v1
* replace function props with "[Function]"

* @vue/compat does not pass slots in $scopedSlots

Updates Rails to the latest version

This avoids a spurious warning from `patch-package` about an out of date
patch successfully applying to `@rails/ujs`.

It seems that
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/124694 correctly
added a new patch for the new version 7.0.5-1, but did not delete the
patch for the old version, 7.0.5.

Updates Rails to the latest version

Changelog: other

Changelog: other

* mimic @vue/test-utils behaviour

* drop unneeded <template functional>

* use custom compiler for webpack and jest
* move :key inside <template v-for>
* fix bug with v-once and v-for

* VUE_VERSION=3 uses Vue.js 3 + gitlab-ui from source
* VUE_VERSION=2 uses Vue.js 2 + gitlab-ui from source
  (mostly for debuggin purposes)
* default behavior should be unchanged

This adds and uses `patch-package` to remove the `data-remote` script
executation behaviour of `@rails/ujs`.

Addresses https://gitlab.com/gitlab-org/gitlab/-/issues/336138.