fix: regen package-lock to fix desync

[Hweinstock]

Description

Regen package-lock to fix failing build.

Related Issue

Closes #

Documentation PR

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

How have you tested the change?

• I ran npm run test:unit and npm run test:integ
• I ran npm run typecheck
• I ran npm run lint
• If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[agentcore-cli-automation]

Reviewed the diff — this PR only modifies package-lock.json (no package.json changes). I verified:

• All 69 root dependencies in package.json are present in the lockfile and resolve to node_modules/ entries.
• All version changes are minor/patch bumps within the existing semver ranges declared in package.json (e.g., @aws-cdk/toolkit-lib 1.25.1 → 1.25.2, @aws-cdk/cloud-assembly-schema 53.23.0 → 53.24.0, @types/node 25.7.0 → 25.8.0, cdk-from-cfn 0.298.0 → 0.299.0).
• uuid@11.1.1 is no longer present, but that's consistent — @aws-cdk/toolkit-lib@1.25.2 removed uuid from its dependency list upstream.
• The 76 added entries are platform-specific optional binaries (@esbuild/*, @rolldown/*, @unrs/resolver-binding-*, lightningcss-*, fsevents) that npm now records as part of optionalDependencies resolution — expected.
• All entries have integrity and resolved fields; lockfile structure is sound.

LGTM. 🚀