Extend the release action to publish a stable veda-ui version to NPM

[dzole0311]

Context

Currently, we have no stable veda-ui registry releases, which causes a lot of inconsistencies in the Next.js repo where developers override each other's changes (e.g., one registry version includes the Footer export while another does not. If the latter gets merged last, then the repo will break).

With the move to NPM (see RFC), we need to streamline the release process to avoid conflicts. The best workflow for our current setup is to extend the biweekly release action to publish a stable NPM release every two weeks from the main branch. Like this we will always rely on stable version with all the accumulated changes rather than branch-specific previews directing the veda-ui version in NextJS.

Acceptance Criteria

• The biweekly release action is extended to publish a stable version of the veda-ui library to npm
• A preview is automatically created in NextJS, bumping the version of the veda-ui

Related Tickets

RFC for context: https://docs.google.com/document/d/1JRvZybU08mSdZTTXPkJr5pqYgoB_5EYYNWixXlgUIlA/edit?tab=t.0

[sandrahoang686]

Question to think about: Some changes will breaking to the NextJs instance but not breaking to legacy, how do we signify that? Currently we prefix PR titles

[aboydnw]

Maybe we can address this when we change #1525

[aboydnw]

Actually, is this done based on the linked PR?

[dzole0311]

@aboydnw This is not yet automated and can be done as part of #1525 (cc @hanbyul-here). Reopened the issue.