feat: Package tag changelog generation [DT-9260]

[lanesawyer]

What

Adds pnpm commands to generates changelogs off of the tags (matching @alleninstitute/[vis-library-name]@#.#.#)

What It Does Not Do

Does not set up a mechanism by which to generate the changelogs. There will be a different PR to set up a GitHub Actions workflow to tag the commit, update the changelog, and publish the package when we push a button.

How

Use the tag pattern to extract the version in each changelog
Add a tag pattern to the command for each to indicate which commits to look for

PR Checklist

• Is your PR title following our conventional commit naming recommendations?
• Have you filled in the PR Description Template?
• Is your branch up to date with the latest in main?
• Do the CI checks pass successfully?
• Have you smoke tested the example applications?
• Did you check that the changes meet accessibility standards?
• Have you tested the application on these browsers?
  • Chrome (Fully supported)
  • Firefox (Major bug fixes supported)
  • Safari (Major bug fixes supported)

[lanesawyer]

@Jarbuckle and @suyli7, this one is in need of review! I'm realizing we never got the changelog generation for vis in, so doing the release for DT-9260 is a little difficult at them moment, since changelog updating should be a part of it!

[Jarbuckle]

Looks fine! Scatterbrain markdown's probably gonna a be a bit janky, but hopefully going forward we'll be fine on that front.