chore: upgrade zod to 3.22.3

[hmacr]

Closes #548

✅ Checklist

• I have followed every step in the contributing guide
• The PR title follows the convention.
• I ran and tested the code works

---

Testing

Ran E2E tests to verify they succeeded.

---

Changelog

Upgrade zod library to 3.22.3 across all packages.

---

Screenshots

💯

[changeset-bot]

🦋 Changeset detected

Latest commit: 1086bb3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 32 packages

Name	Type
@trigger.dev/airtable	Patch
@trigger.dev/supabase	Patch
@trigger.dev/typeform	Patch
@trigger.dev/sdk	Patch
@trigger.dev/github	Patch
@trigger.dev/linear	Patch
@trigger.dev/stripe	Patch
@trigger.dev/slack	Patch
@trigger.dev/testing	Patch
@trigger.dev/react	Patch
@trigger.dev/core	Patch
@trigger.dev/cli	Patch
@references/job-catalog	Patch
@references/nextjs	Patch
@references/package-tester	Patch
perf	Patch
astro-example	Patch
@references/remix	Patch
@references/unit-testing	Patch
@trigger.dev/tailwind-config	Patch
@trigger.dev/tsconfig	Patch
@trigger.dev/astro	Patch
@trigger.dev/eslint-plugin	Patch
@trigger.dev/express	Patch
@trigger.dev/integration-kit	Patch
@trigger.dev/nextjs	Patch
@trigger.dev/remix	Patch
@trigger.dev/openai	Patch
@trigger.dev/plain	Patch
@trigger.dev/replicate	Patch
@trigger.dev/resend	Patch
@trigger.dev/sendgrid	Patch

Not sure what this means? Click here to learn what changesets are.

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

[ericallam]

This looks great! Could you resolve the conflicts and then this PR can be merged 👍

[hmacr]

Thanks! I've rebased the PR.

[ericallam]

@hmacr unfortunately the pnpm-lock.yaml file in this PR is broken, probably because of a bad merge or conflict resolution. Might be easiest to close this PR and redo the changes on top of the newest main broken lockfile. Doing a pnpm install with a broken lockfile completely recreates the lockfile which is definitely not what we want.

[hmacr]

@ericallam ah ok. Let me close this and create a new PR.

[hmacr]

@ericallam Raised a new PR - #570. Please check.

Unfortunately, I was using pnpm v8 (instead of the recommended v7). v8 introduced a change in the lockfile format, hence it resulted in too many changes.