chore: regenerate lockfile

[AllanZhengYP]

Description of changes

Issue #, if available

Description of how you validated changes

Checklist

• Have read the Pull Request Guidelines
• PR description included
• yarn test passes and tests are updated/added
• PR title and commit messages follow conventional commit syntax
• If this change should result in a version bump, changeset added (This can be done after creating the PR.) This does not apply to changes made to docs, e2e, examples, or other private packages.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 26bd1ff

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ashika112]

You might have to wait till Chris's PR goes in to get this going 😅

[dindjarinjs]

Let's scope the changes just to aws-amplify packages

[AllanZhengYP]

This change does not need to be merged, but only to make sure the CI would pass with the lastest storage-browser-integrity tag.