SW-1095: Added github actions for alpha/beta publishing

[darwinboersma]

JIRA ticket

https://tetrascience.atlassian.net/browse/SW-1095

Code changes

Added GH workflows for publishing the package on PR and on merge to main branch (alpha and beta publishing, respectively)

QA

Publishing this PR and merging it will allow me to confirm that the actions function as expected

Checklist before requesting a review

• I have performed a self-review of my code on localhost and it looks good
• I added proper Description both to pr and jira ticket

[augmentcode]

🤖 Augment PR Summary

Summary: This PR adds GitHub Actions workflows to publish ts-lib-ui-kit pre-releases to the internal registry for easier validation.

Changes:

• Added a pull_request-triggered workflow to build and publish an alpha package for PR validation.
• Added a push-to-main workflow to build and publish a beta package after merges.
• Both workflows configure Yarn to use JFrog Artifactory (read registry for installs, then switch to write registry for publishing).
• Version is auto-suffixed with -alpha.${{ github.run_number }} or -beta.${{ github.run_number }} before publishing.

Technical Notes: Uses Node 20, Yarn dependency caching, and yarn npm publish with npm dist-tags (alpha/beta).

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

This workflow runs on pull_request but uses Artifactory write secrets later; that can both fail for forked PRs (secrets unavailable) and expose secrets to untrusted PR code in same-repo contributions. Consider gating the job to non-fork PRs / trusted actors (or using a pull_request_target-based flow with careful checkout) to avoid accidental secret exposure.

_{🤖 Was this useful? React with 👍 or 👎}