chore(shared): update packages

[designcode]

Note

Medium Risk
Primarily dependency bumps, but includes upgrading @tigrisdata/storage to ^3.1.0 and AWS SDK/Sмитhy packages, which could change runtime behavior in storage/S3 interactions.

Overview
Updates monorepo dependency versions across root and workspace packages.

Notably bumps tooling (eslint, prettier, typescript-eslint, vitest) and updates runtime deps like dotenv, react/react-dom, and jsdom. Internal consumers (keyv-tigris, react) are moved from @tigrisdata/storage@^2.15.6 to ^3.1.0, and packages/storage updates its AWS S3 SDK and related @smithy/* versions accordingly, with a refreshed package-lock.json.

^{Reviewed by Cursor Bugbot for commit 96eb595. Bugbot is set up for automated code reviews on this repo. Configure here.}

[greptile-apps]

Greptile Summary

This PR bumps third-party dependency versions across all four workspace packages and the repo root — AWS SDK packages to ^3.1030.0, dotenv to ^17.4.2, vitest to ^4.1.4, and various React/tooling packages — with a regenerated package-lock.json that resolves all direct deps to the new minimum versions.

Confidence Score: 5/5

• Safe to merge — all package version specifiers are consistent with the lock file and the only finding is a pre-existing workspace isolation pattern that is not introduced or worsened by this PR.
• All direct dependencies resolve correctly in the lock file. The workspace isolation concern (keyv-tigris and react depending on registry @tigrisdata/storage@3.1.0 rather than local 0.0.1) predates this PR and is unaffected by the changes. No P0 or P1 issues found.
• packages/keyv-tigris/package.json and packages/react/package.json — both reference @tigrisdata/storage@^3.1.0 against a local 0.0.1 workspace, causing the registry package to be used instead of local code during testing.

Important Files Changed

Filename	Overview
package.json	Root devDependencies updated (commitlint, eslint v10, prettier, tsup, typescript, vitest v4, etc.) — all version specifiers align with lock file resolutions.
packages/storage/package.json	AWS SDK and smithy packages bumped to ^3.1030.0 / ^5.3.13, dotenv bumped to ^17.4.2; lock file resolves each to the specified minimum, no inconsistencies.
packages/iam/package.json	Only change is dotenv bumped to ^17.4.2, consistent with other packages.
packages/keyv-tigris/package.json	keyv bumped to ^5.6.0, dotenv to ^17.4.2; depends on @tigrisdata/storage@^3.1.0 which doesn't satisfy the local workspace version (0.0.1), so npm resolves against the published registry package instead of local workspace code.
packages/react/package.json	React/RTL/jsdom devDeps updated; same workspace isolation issue — @tigrisdata/storage@^3.1.0 resolves to the registry-published 3.1.0 rather than the local workspace package (0.0.1).
package-lock.json	Lock file updated and generally consistent with package.json changes; packages/keyv-tigris and packages/react each have their own node_modules/@tigrisdata/storage resolved from the registry at 3.1.0 (with its older dep ranges ^3.1018.0) rather than the local workspace.

_{Reviews (1): Last reviewed commit: "chore(keyv-tigris): update packages" | Re-trigger Greptile}