Scaffold each framework package, connect to Next doc site about skeleton HOT 1 OPEN

@niktek @AdrianGonz97 currently I've accomplished the following on the linked PR:

1. Removed the Vue package
2. Update the dependencies for the React/Svelte packages
3. Created an index.ts export for either package
4. Implemented the Skeleton Tailwind plugin (via workspaces) per package
5. Implemented basic routing for the Vite/React project using vite-remix-router
6. Create a simple split column navigation for either local package project (see screenshot below)
7. Linked the React package to the Astro doc site using PNPM workspaces
8. Linked the Svelte package to the Astro doc site using PNPM workspaces (but disabled due to error; described below)

We should now be able to test components both within their respective local package projects, as well as within the Astro doc site.

Local Project UI + Routing

Here's what the local project route navigation UI looks like:

Svelte Issue (on deployment only)

Per the Svelte project - I've sadly had to disable this from the Astro project. The moment it's linked via workspace settings the deployment fails. My guess is it's not happy with the package.json settings -OR- something specifically about how the project is constructed.

In the Astro docs project you can quickly re-enable the Svelte package by doing the following:

1. Within the package.json, add: "@skeletonlabs/skeleton-react": "workspace:^",
2. Run pnpm i to ensure this is added
3. Open /src/examples/resources/test/ExampleSvelte.svelte and re-enable the import + component
4. This component is used in /src/content/resources/test.mdx
5. Point your browser to /resources/test to preview

Again this will work when tested locally, but cause the deployment to fail with the following errors:

I'd welcome you guys giving this a once over to help troubleshoot.

from skeleton.