fix(deps): update dependency @duckdb/duckdb-wasm to v1.33.1-dev45.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@duckdb/duckdb-wasm	1.32.0 → 1.33.1-dev45.0

---

Release Notes

duckdb/duckdb-wasm (@​duckdb/duckdb-wasm)

v1.33.1-dev45.0

Compare Source

v1.33.1-dev44.0

Compare Source

v1.33.1-dev43.0

Compare Source

v1.33.1-dev42.0

Compare Source

v1.33.1-dev41.0

Compare Source

v1.33.1-dev40.0

Compare Source

v1.33.1-dev4.0

Compare Source

v1.33.1-dev39.0

Compare Source

v1.33.1-dev38.0

Compare Source

v1.33.1-dev37.0

Compare Source

v1.33.1-dev36.0

Compare Source

v1.33.1-dev35.0

Compare Source

v1.33.1-dev34.0

Compare Source

v1.33.1-dev20.0

Compare Source

v1.33.1-dev19.0

Compare Source

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: viewer/pnpm-lock.yaml

Scope: all 6 workspace projects
? Verifying lockfile against supply-chain policies (957 entries)...
✗ Lockfile failed supply-chain policy check (957 entries in 4.1s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  astro@6.4.6 was published at 2026-06-10T17:28:36.000Z, within the minimumReleaseAge cutoff (2026-06-10T14:40:15.475Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.