NEXT: Update Svelte/React packages to utilize PNPM Catalogs for version syncing

[endigo9740]

Following our recent integration of Zag.js, we've learned that each individual Zag component is installed as it's own separate package per framework. For example:

"@zag-js/accordion": "^0.65.0",
"@zag-js/avatar": "^0.65.0",
"@zag-js/progress": "^0.65.0",
"@zag-js/radio-group": "^0.65.0",
"@zag-js/rating-group": "^0.65.0",
"@zag-js/react": "^0.65.0",
"@zag-js/switch": "^0.65.0",
"@zag-js/tabs": "^0.65.0",

These versions must stay in sync to ensure these components remain operational and type data resolves as expected.

@Hugos68 and @AdrianGonz97 have determined a potential solution for this using PNPM catalogs. This will provide a variable in place of the version number that we can control within the monorepo and ensure these remain in sync.

If necessary we should update any related contributor documentation around this. Specifying a minimum version of PNPM to use, etc.

Goals:

• Implement PNPM catalogs for Zag in our Svelte/React packages
• Ensure all Skeleton team members make local updates (update PNPM, etc)
• Document requirements for contributors

[endigo9740]

@Hugos68 @AdrianGonz97 feel free to correct me on any of this if I've mispoken!