[web] add PostgreSQL backend support

[alex-holovach]

Added PostgreSQL as a backend option in the web UI settings, allowing users to view workflow data stored in a postgres database.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5119a05

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

[vercel]

@alex-holovach is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[VaguelySerious]

LGTM! Before we merge, can you add a changeset (pnpm changeset) with a patch change for web?

My other comment is relevant, but not in the way of merging this, and if you decide not to add that to this PR, I'll create a GH issue for it instead

[VaguelySerious]

⚠️ If we're going down the route of adding more world support to the UI, which I'd love to do even for third-party worlds, I think we should not import the world into web.

Instead, we should set the worlds as peer dependencies (or not put them in package.json at all), and when the web app first loads, validateWorldConfig or a similar server action should check the list of known package (or the package name manually provided) to see which of them are installed, and then disable + display tooltip warnings for those that aren't, mentioning e.g. npm install <package-name> to the user.

We expect users to not run into this, since presumably in order to use the o11y UI with their preferred world, they likely already use the world package locally, and must have had it installed, but if not, this prompts them to do so.