build(deps): harden docs site dependencies

[Rishabh060105]

Refs #519

Changes

• Updated the docs app direct dependency axios from ^0.21.2 to ^1.15.0.
• Updated the docs app direct dependency qs from ^6.9.6 to ^6.15.1.
• Regenerated website/package-lock.json while preserving lockfile v2.
• Left docusaurus, remarkable-admonitions, and jsdoc-to-markdown unchanged.

Flags

• This PR intentionally references, but does not close, Outdated docs site dependencies create security and maintenance risk #519 because it is an incremental dependency-hardening change.
• docusaurus@1.14.7 is already the latest Docusaurus v1 package.
• The remaining Highlight.js v9 EOL warning is inherited through the Docusaurus v1 dependency tree and requires a Docusaurus v3 migration rather than a direct dependency bump.
• npm audit --omit=dev still reports remaining vulnerabilities: 107 total, including 47 high and 7 critical, mostly through the old Docusaurus v1 dependency tree.
• The Netlify deploy preview appears to show a generic 404 / asset-path issue, but the local Docusaurus v1 build succeeds and generates the site at website/build/techdocs/index.html. This PR only updates direct dependency metadata and the lockfile; it does not change Docusaurus config, routes, CSS, JS, or docs content. The preview likely needs Netlify to publish website/build/techdocs rather than website/build.

Screenshots or Video

N/A - dependency metadata and lockfile update only.

Related Issues

• Issue Outdated docs site dependencies create security and maintenance risk #519
• Pull Request Upgrade to Docusaurus and Migrate to vNext #505
• Pull Request Update axios and qs dependencies to latest versions #522

Verification

• npm install
• npm run build
• npm audit --omit=dev
• Smoke-checked generated output at website/build/techdocs

Author Checklist

• Ensure you provide a DCO sign-off for your commits using the --signoff option of git commit.
• Vital features and changes captured in unit and/or integration tests
• Commits messages follow AP format
• Extend the documentation, if necessary
• Merging to master from fork:branchname
• Manual accessibility test performed
  • Keyboard-only access, including forms
  • Contrast at least WCAG Level A
  • Appropriate labels, alt text, and instructions