ci: add workflows for automated release & publish

[legobeat]

• Add workflows for automated release and publishing using GitHub Actions
  • Publish nodejs version set to 20.x since these MetaMask actions require at least node v16.
  • Requires new secret NPM_TOKEN on repo environment npm-publish
• ci: Add linting of CHANGELOG.md
  • An older version of @metamask/auto-changelog is used to remain runnable in unified build-lint-test job.
  • Update CHANGELOG.md to pass linting
• ci: upgrade actions/checkout to v4
• ci: upgrade actions/node from v1 to v3

Workflows lifted from @metamask/oss-attribution-generator, which is another remaining yarn v1 package in the org, updated and amended.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/auto-changelog@2.6.1	Transitive: environment, filesystem, shell	+16	1.23 MB	gudahtt
npm/@types/babel__traverse@7.11.0	None	0	63.1 kB	types
npm/@types/istanbul-lib-coverage@2.0.3	None	0	5.91 kB	types
npm/import-fresh@3.3.0	Transitive: filesystem, unsafe	+3	19.8 kB	sindresorhus
npm/is-symbol@1.0.4	None	0	22 kB	ljharb
npm/onetime@5.1.2	None	+1	10.6 kB	sindresorhus
npm/signal-exit@3.0.7	None	0	9.96 kB	isaacs

🚮 Removed packages: npm/@babel/helper-plugin-utils@7.8.3, npm/@babel/parser@7.21.4, npm/@babel/template@7.20.7, npm/@babel/types@7.21.4, npm/@types/babel__traverse@7.0.8, npm/@types/istanbul-lib-coverage@2.0.1, npm/import-fresh@3.2.1, npm/is-glob@4.0.1, npm/is-symbol@1.0.3, npm/picomatch@2.2.2, npm/signal-exit@3.0.2

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/diff@5.2.0

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[legobeat]

@SocketSecurity ignore npm/diff@5.2.0

new author ok