feat: add release gh actions

[V00D00-child]

What

Add release gh actions to distribute Kernel / Gator snap via npm.

How

We use create-release-branch to create the releases, instead of the create-release-pr workflow in the module template.

For a monorepo we are using an "independent" versioning strategy, and release are trigger via the command line using create-release-branch tool.

Refer to the usage documentation we preparing a release. The tool needs to know two things:

1. Which packages you want to release and how to set the version for each package.
2. Whether or not you are creating a backport release as opposed to an "ordinary" release.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/action-utils@1.1.1	filesystem	0	50 kB	lgbot
npm/@metamask/auto-changelog@4.1.0	Transitive: environment, shell	+10	376 kB	metamaskbot
npm/@metamask/create-release-branch@4.1.1	None	0	663 kB	metamaskbot
npm/@metamask/superstruct@3.2.1 ➜ 3.1.0	None	0	437 kB	metamaskbot
npm/@noble/curves@1.1.0	None	0	1.3 MB	paulmillr
npm/@noble/hashes@1.5.0	None	0	837 kB	paulmillr
npm/@scure/base@1.1.3	None	0	77.8 kB	paulmillr
npm/@scure/bip32@1.3.1	None	0	55.7 kB	paulmillr
npm/@scure/bip39@1.2.1	None	0	357 kB	paulmillr
npm/@types/debug@4.1.12 ➜ 4.1.7	None	0	7.22 kB	types
npm/@types/ms@2.1.0 ➜ 0.7.31	None	0	2.88 kB	types
npm/@types/semver@7.5.4 ➜ 7.7.0	None	0	23.3 kB	types
npm/bundle-name@4.1.0	None	0	3.15 kB	sindresorhus
npm/default-browser-id@5.0.0	None	0	3.02 kB	sindresorhus
npm/default-browser@5.2.1	None	0	5.82 kB	sindresorhus
npm/define-lazy-prop@3.0.0	None	0	4.42 kB	sindresorhus
npm/diff@5.2.0 ➜ 5.0.0	None	0	369 kB	kpdecker
npm/ethereum-cryptography@2.1.2	None	+1	827 kB	paulmillr
npm/open@10.1.0	environment	0	55.2 kB	sindresorhus
npm/run-applescript@7.0.0	None	0	5 kB	sindresorhus
npm/validate-npm-package-name@5.0.1 ➜ 5.0.0	None	0	7.88 kB	lukekarrys

🚮 Removed packages: npm/es-define-property@1.0.0, npm/gopd@1.0.1, npm/has-symbols@1.0.3, npm/object-inspect@1.13.1, npm/side-channel@1.0.4

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/validate-npm-package-name@5.0.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

[V00D00-child]

@SocketSecurity ignore npm/validate-npm-package-name@5.0.0

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[jeffsmale90]

This looks good - just one comment on a typo, and some additional changes that could come later.