Pin npm version and canonicalize lockfile

Salim Zidanerequested to merge
gitlab-community/gitlab-org/developer-relations/contributor-success/contributors-gitlab-com:489/pin-npm-canonicalize-lockfile into main

What does this MR do and why?

Related to #489

First step of the implementation plan to fix peer/dev flag changes:

  • Adds "packageManager": "npm@11.18.0" to package.json with an engine-strict=true rule
  • Creates a new package-lock.json based on npm 11.18.0

Validation Steps

npm run coverage
npm run build
npm run lint

/cc @leetickett-gitlab

Edited by Salim Zidane

Merge request reports