chore(NODE-6118): generate authorized publisher report and compliance report

[baileympearson]

Description

What is changing?

Authorized publisher reports and compliance reports are generated during the main and 5.x releases.

Example successful CI run: https://github.com/mongodb/node-mongodb-native/actions/workflows/release.yml

Here's an example authorized publisher report:

Product: node-mongodb-native
Version: 
Releaser: Bailey Pearson
Build Source: GitHub Actions
Build Number: 9600830984
Filename: mongodb-6.7.0.tgz
Shasum: 41d7f96711c3b309201b850162e484c08f[79](https://github.com/mongodb/node-mongodb-native/actions/runs/9600830984/job/26478024665#step:7:81)cb008b96ebdfc177ecae0f43edb0
Filename: mongodb-6.7.0.tgz.sig
Shasum: fea5d7a0ae385b7186faac73f49732a89d14d3[80](https://github.com/mongodb/node-mongodb-native/actions/runs/9600830984/job/26478024665#step:7:82)b5e83d507fb74675ca7b7023

Here's an example compliance report:

Release Creator
Bailey Pearson

Tool used to track third party vulnerabilities
Silk

Third-Party Dependency Information
See sbom.json

Static Analysis Findings
See sarif-report.json

Signature Information
See authorized-publication.txt

Security Report
See https://github.com/mongodb/node-mongodb-native/blob/6.7.0/tbd

Known Vulnerabilities
Any vulnerabilities that may be shown in the files referenced above have been reviewed and accepted by the appropriate approvers.

Is there new documentation needed for these changes?

What is the motivation for this change?

Release Highlight

Fill in title or leave empty for no highlight

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

[aditi-khare-mongoDB]

LGTM, dry_run vars also looks good, moving to team review.