Move off of npm

[shawninder]

It's costing way too much with all the external collaborators, I was mistaken about the pricing scheme.

I think we can just use GitHub, but let's keep the built files in a separate, dedicated and fully automated branch, perhaps called dist? I suppose this would mean including the library as a dependency using this in package.json:

"@tjikko/components": "git@github.com:tjikko-studio/components@v1.3.30#dist"

Not 100% sure about the syntax, but this should work unless Microsoft broke this already as well

[shawninder]

This issue involves:

• Reworking the deploy script to publish the package to a separate GitHub branch rather than deploying to npm
• Fetching the component library from this new location in the backend and frontend and anywhere else the component library may be imported from
• Testing locally that everything still works as expected, both when the repos are linked and when they aren't
• Deploying this change and making sure that things work in the GitHub Action runner as well as on the production machine (prod should still work)

[shawninder]

Done, the components are now being published to the GitHub Package Registry as @tjikko-studio/components