Update Rancher Components release to use trusted providers

[rak-phillip]

Summary

This updates the Rancher Components release to use trusted providers instead of the npm token.

Occurred changes and/or fixed issues

• Update Rancher Components release to use trusted providers

Technical notes summary

See the trusted publishing docs on npm¹. This is now the preferred approach to publishing packages.

I'm using Rancher Components as a test bed because releases are infrequent and usage is limited to the point where we are allowed to experiment more freely.

Areas or cases that should be tested

After merge, release a new version of Rancher Components.

Areas which could experience regressions

Publishing Rancher Components.

Screenshot/Video

NA

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
• The PR has been reviewed in terms of Accessibility
• The PR has considered, and if applicable tested with, the three Global Roles Admin, Standard User and User Base

Footnotes

1. https://docs.npmjs.com/trusted-publishers ↩