chore: add a 6.8 release process workflow

[nbbeeken]

Description

What is changing?

• Add a workflow for releasing from 6.8

Is there new documentation needed for these changes?

No

What is the motivation for this change?

Automated releases from 6.8

Double check the following

• Ran npm run check:lint script
• Self-review completed using the steps outlined here
• PR title follows the correct format: type(NODE-xxxx)[!]: description
  • Example: feat(NODE-1234)!: rewriting everything in coffeescript
• Changes are covered by tests
• New TODOs have a related JIRA ticket

[nbbeeken]

3c3
<     branches: [5.x]
---
>     branches: [6.8]
11c11
< name: release-5x
---
> name: release-68
22c22
<           target-branch: 5.x
---
>           target-branch: 6.8
78c78
<           sarif_report_target_ref: 5.x
---
>           sarif_report_target_ref: 6.8
102c102,104
<       - run: npm publish --provenance --tag=5x
---
>         # Just picking a string to put here so that releases from this branch are not marked "latest",
>         # we should go and rm-dist-tag after this is published, no reason to keep it tagged.
>       - run: npm publish --provenance --tag=stable

The diff against release-5.x.yml

For the npm tag we could use what typescript does: "tag-for-publishing-older-releases" 😅 I think we should just delete the tag anyway so this isn't for public consumption.

[nbbeeken]

Per slack convo, remove temp tag after publish