feat: Publish Veda UI to npm and workflow proposal

[dzole0311]

Related Ticket: closes #1369

Description of Changes

• Changed the registry in .npmrc from the private Verdaccio registry to the public NPM registry under the scope teamimpact
• Published the library under the teamimpact scope and updated the docs on how to set the necessary npm credentials
• Experimented with a new README-lib.md:
  • Added an experimental workflow to copy this file to the lib dist during the library build
  • This allows us to have a unique README.md for the library when its published on NPM, separate from the veda-ui submodule documentation
• I noticed the lib bundle size increased, largely due to the USWDS images and fonts being copied in the library build. There’s room for optimization, including removing unused assets or modules from the existing veda-ui (e.g. air-quality-and-covid-19--story-cover.png etc), and I made a tracking issue for that: Optimize veda-ui library bundle size #1392

Notes & Questions About Changes

Proposed workflow for developing, testing and publishing the NPM registry:

• Workflow proposal for veda-ui NPM publishing and development / testing with consuming apps (Next.JS) is documented here. The proposal aligns and extends our current veda-ui publishing workflow with the bi-weekly automated releases

Validation / Testing

1. Set the necessary npm auth credentials mentioned in the set up docs
2. dry-run publish a version to make sure everything you're correctly authenticated
3. Review the Google doc proposal and share feedback

[netlify]

✅ Deploy Preview for veda-ui ready!

Name	Link
🔨 Latest commit	dc629cf
🔍 Latest deploy log	https://app.netlify.com/sites/veda-ui/deploys/67a1e02e09b1b20008876375
😎 Deploy Preview	https://deploy-preview-1391--veda-ui.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sandrahoang686]

Was able to publish @teamimpact/[email protected] following instructions. See pic. Version has been unpublished.

[AliceR]

I published a version from my aoi-simplification branch, see https://www.npmjs.com/package/@teamimpact/veda-ui/v/5.11.7-1395.0
It works! No I am off to test my work on next-veda 🚀

Thanks for all your work here @dzole0311 🎉

[dzole0311]

Summary from the RFC:

1. Development and testing

• Work happens in feature branches as now
• Before merging, if a change is needed for Next.js, we publish a pre-release version under the preview tag for testing
• A preview PR is opened on the instance side to validate changes before merging

2. Peer review and approvals

• Once tested in next-veda-ui, changes get merged into main
• Preview PRs are for validation only and shouldn’t be merged into next-veda-ui/main

3. Bi-Weekly automated releases

• Every two weeks, the GitHub release action publishes a stable version (Extend the release action to publish a stable veda-ui version to NPM #1419)
• Version bumps follow semantic versioning (major/minor/patch)
• Once released, an automatic PR updates the dependency in the instance repo

4. Cleanup

• Old pre-release versions (preview tags) are removed from NPM to keep things clean (Clean up stale preview NPM versions #1420)

Action items:

1. Extend the release action to publish a stable veda-ui version to NPM #1419
2. Clean up stale preview NPM versions #1420

Reassess if the workflow should be refined as needed after starting the development work.