fix: sync package-lock.json version fields during automated version bump

[Copilot]

Description

scripts/bump-version.js updated package.json on version bumps but left package-lock.json stale — both its top-level version and packages[""].version fields. This caused the lockfile to drift out of sync after every automated bump.

Changes to scripts/bump-version.js:

• Added packageLockJsonPath constant
• Added updatePackageLockJson — updates lock.version and lock.packages[""].version; gracefully no-ops if the file doesn't exist
• Calls updatePackageLockJson from main() alongside updatePackageJson
• Updated JSDoc header to list package-lock.json as a managed file

[bump-version] patch: 1.113.3  →  1.113.4

  public/versioning.js  →  1.113.4
  package.json          1.113.3  →  1.113.4
  package-lock.json     1.113.3  →  1.113.4
  src/index.html        (no changed public/*.js files detected)

Type of change

• Bug fix
• New feature
• Refactoring / style
• Documentation update / chore
• Other (please describe)

Versioning

• Version is updated
• Changed files hash is updated

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

Keeps the repo’s automated version-bump script from leaving package-lock.json out of sync with package.json, preventing lockfile drift after each bump.

Changes:

• Added a package-lock.json path constant to the bump script.
• Implemented updatePackageLockJson to update package-lock.json’s top-level version and packages[""].version fields (skips if missing).
• Wired the new lockfile update into main() and updated the script header docs.