Svelte Support

[garrett-from-chainlift]

This task is for tracking progress on Svelte support.

[JosefSaltz]

I'm currently planning on staging the final PR for review, squashed with only the converted components living under registry/svelte. As far as I know this would still require combining the package.json to contain all the cross-library dependencies under the same file. Is this ideal for distribution going forward or is there a better way to handle this as a monorepo?

I've also had to extend and replace some types to decouple them from being attached to React and its relevant expectations. Example: the React.HTMLAttributes is being substituted out for HTMLAttributes from svelte/element. However some of the Lk* based types are still dependent on React library (JSX.IntrinsicElements for LkSemanticTag) and those are a bit harder to adapt. I'd like to change as little existing code as possible and leave that to the Chainlift team and only be filing additions for the project to build off of so please let me know how I can approach this without major disruption.