Adjust cicd workflows to publish release and snapshot/prerelease tags slightly differently.

[greinard]

Overview

This change is necessary to ensure that snapshot/pre-release tags do not result in populating the latest version of the library. Otherwise, feature branch pre-releases can get picked up as the latest version.

Security

REMINDER: All file contents are public.

• I have ensured no secure credentials or sensitive information remain in code, metadata, comments, etc.
  • Please verify that you double checked that .storybook/preview.js does not contain your participant access key details.
  • There are no temporary testing changes committed such as API base URLs, access tokens, print/log statements, etc.
• These changes do not introduce any security risks, or any such risks have been properly mitigated.

Describe briefly what security risks you considered, why they don't apply, or how they've been mitigated.

• This change adds a further limitation to publishing to help ensure that feature branch pre-releases are not picked up as the latest version of the library from npm.

Checklist

Testing

This change is related to build/deploy config, not the app functionality itself. Testing of the build/deploy config will be performed as soon as changes are available on main.

Documentation

N/A - Other than a possible update to the README to describe how to use the Snapshot.ps1 script.