chore(deps): bump qs from 6.13.1 to 6.14.1 in /api-docs

[dependabot]

Bumps qs from 6.13.1 to 6.14.1.

Changelog

Sourced from qs's changelog.

6.14.1

• [Fix] ensure arrayLength applies to [] notation as well
• [Fix] parse: when a custom decoder returns null for a key, ignore that key
• [Refactor] parse: extract key segment splitting helper
• [meta] add threat model
• [actions] add workflow permissions
• [Tests] stringify: increase coverage
• [Dev Deps] update eslint, @ljharb/eslint-config, npmignore, es-value-fixtures, for-each, object-inspect

6.14.0

• [New] parse: add throwOnParameterLimitExceeded option (#517)
• [Refactor] parse: use utils.combine more
• [patch] parse: add explicit throwOnLimitExceeded default
• [actions] use shared action; re-add finishers
• [meta] Fix changelog formatting bug
• [Deps] update side-channel
• [Dev Deps] update es-value-fixtures, has-bigints, has-proto, has-symbols
• [Tests] increase coverage

Commits

• 3fa11a5 v6.14.1
• a626704 [Dev Deps] update npmignore
• 3086902 [Fix] ensure arrayLength applies to [] notation as well
• fc7930e [Dev Deps] update eslint, @ljharb/eslint-config
• 0b06aac [Dev Deps] update @ljharb/eslint-config
• 64951f6 [Refactor] parse: extract key segment splitting helper
• e1bd259 [Dev Deps] update @ljharb/eslint-config
• f4b3d39 [eslint] add eslint 9 optional peer dep
• 6e94d95 [Dev Deps] update eslint, @ljharb/eslint-config, npmignore
• 973dc3c [actions] add workflow permissions
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[sentry]

Bug: The PR claims to bump the qs package for a security fix, but the lockfile changes do not actually apply this update.
_{Severity: HIGH | Confidence: High}

🔍 Detailed Analysis

The pull request's title and description state an intent to bump the qs package from version 6.13.1 to 6.14.1. This update is noted to contain a critical security fix. However, the actual changes within the api-docs/pnpm-lock.yaml file do not include this version bump for qs. While the lockfile is internally consistent and will not cause a runtime crash, it fails to incorporate the intended security patch, leaving the dependency at the older, vulnerable version.

💡 Suggested Fix

Regenerate the lockfile to correctly bump the qs package from version 6.13.1 to 6.14.1 as stated in the pull request's description. Ensure that the pnpm-lock.yaml reflects the updated version and its resolved dependencies.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: api-docs/pnpm-lock.yaml#L331-L342

Potential issue: The pull request's title and description state an intent to bump the
`qs` package from version 6.13.1 to 6.14.1. This update is noted to contain a critical
security fix. However, the actual changes within the `api-docs/pnpm-lock.yaml` file do
not include this version bump for `qs`. While the lockfile is internally consistent and
will not cause a runtime crash, it fails to incorporate the intended security patch,
leaving the dependency at the older, vulnerable version.

_{Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 8091481}