Update "Releases" page when a new tag is pushed to repo

[anmolshres98]

Closes #229

This PR makes it so that every time a package is published to npm and a tag is created then pushed to this repo, the newly created script

• discerns the packageName and version from the tag
• determines what the package directory is and the CHANGELOG md for the package would be
• extracts the relevant release notes for the current tagged release
• determines and creates zipped artifacts for the specific package
• uses gh cli to create a new release using the triggered tag containing above parsed release notes and artifacts

Testing:

• one of the missing release created using the new workflow: https://github.com/iTwin/auth-clients/releases/tag/%40itwin%2Fservice-authorization_v1.2.3
• a test release auto-triggered and created by the pipeline when a test tag is pushed to this repo: https://github.com/iTwin/auth-clients/releases/tag/%40itwin%2Ftester_v1.0.1 (I will delete this test release and the test tag once this PR is merged)

[anmolshres98]

The Create GitHub Release workflow here is being reported as failed as it was forced to fail on purpose during a test. Check this comment for details: #281 (comment)

[DanRod1999]

Didn't look to close into this, but is creating a release using this action step potentially an option?
https://github.com/actions/create-release

we should also be trying to leverage to tools actions have as much as we can I think. Its what we currently in ado at least.

[aruniverse]

Didn't look to close into this, but is creating a release using this action step potentially an option? actions/create-release

we should also be trying to leverage to tools actions have as much as we can I think. Its what we currently in ado at least.

I agree we should look at using existing tools instead of rolling our own if possible.
But what Dan linked has been archived and no longer supported, plz dont use it