feat(@workflow/world-postgres): implemented a script for setting up the required tables

[karthikscale3]

Summary

The @workflow/world-postgres package currently requires users to manually copy and run SQL queries to set up the required database tables. This PR simplifies the setup process by:

1. Exporting the database schema - Users can now import schema definitions programmatically
2. Adding a CLI tool - One-command database setup with .env file support
3. Including migration SQL files - SQL files are now part of the published package

Usage

pnpm exec workflow-postgres-setup

Output:

🔧 Setting up database schema...
📍 Connection: postgres://postgres:****@db.yourcloudprovider.co:5432/postgres
✅ Database schema created successfully!

Created tables:
  - workflow_runs
  - workflow_events
  - workflow_steps
  - workflow_hooks
  - workflow_stream_chunks

[changeset-bot]

🦋 Changeset detected

Latest commit: b3d05ba

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

This PR includes changesets to release 1 package

Name	Type
@workflow/world-postgres	Minor

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

[vercel]

@karthikscale3 is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

spam

[pranaygp]

question for @Schniz - curious if we could just keep this as the main bin? that way npx @workflow/world-postgres

i'm indifferent

[VaguelySerious]

Not a strong opinion, but I think since it's a one-time setup script separate from regular intended execution, it makes sense for it to be named like it's in the PR

[pranaygp]

LGTM but will let @VaguelySerious or @Schniz do the final stamp! thank you so much :)

[VaguelySerious]

LGTM! Thanks for polishing the setup

[VaguelySerious]

This seems like it's not needed given we except this to either be imported by the bin (and run), or imported in a module