feat: add multi-schema support

[KayleeWilliams]

Currently FumaDB can only be used once per database. This can be troublesome if I have multiple packages that use FumaDB that i want to host on my database, or if I am creating a managed service and want to use the same backend as self-host would then many customers can exist on the same database without having to do 1 customer per db which can be expensive.

I've mostly tested this with Postgres so not 100% sure on the compatibility with other DBs although i've tried to look into that, like with MongoDB we just need to add a prefix for example.

Also ran the formatter so some non-worked on files might have gotten added here.

[changeset-bot]

⚠️ No Changeset found

Latest commit: aa2d6d3

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]

@KayleeWilliams is attempting to deploy a commit to the Fuma Team on Vercel.

A member of the Team first needs to authorize it.

[KayleeWilliams]

@fuma-nama what do you think of this? At least idea wise

[fuma-nama]

Thanks for the PR!

Looks good to me, I think it's a reasonable inconsistency to add, probably even better to have jsdoc on which database is supported.