In order to test our artifacts before a release, we can merge the two pipelines we currently have: PR (builds and runs tests) and Release (builds and releases).

These are currently under the same "workflow" in CircleCI but are split based on a filter which checks if the branch is "master". By removing this filter, the pipelines can be merged. We'll keep the "master" filter as a prerequisite for release.

We now also build once so we can see what was generated and test them. The release job only uploads files.

Lerna is no longer needed as npm workspaces provides better support for this separated build, test, release workflow.

The "should-release" approval step is temporary so that we can manually validate the new pipeline's artifacts are correct on master.

To make sure we've built it correctly. Also removes the need to build the tarball twice.

Like we do with our various other artifacts to ensure they're not
corrupt before release.

I've also renamed the tarballs to remove the version so that they're
less dynamic and easier to work with. The version is within the tarball,
the filename isn't used for anything special.

So that they're easier to keep track of.

We often get questions on how to contribute to this repo. What versions to use, what the workflow is, etc. This PR updated our CONTRIBUTING guide to answer that.

I've also left a notice for external contributors on how we prefer to handle external contributions.

docs: update contributing guide

This ensures our Windows builds are valid before release.

I've removed `npm_version` from analytics as it's only relevant for
OSS NPM scans rather than being "standard data".

Also made general analytics test changes so that they're more flexible
to different test environments.

chore(ci): merge release and pr pipelines

Bumping snyk-docker-plugin to 4.34.5 which fixes invalid dep-graph in Maven
projects causing issues with calculating a package's vulnerable paths

Update filepath in codeowners after rename

fix: Invalid JAR fingerprints for Maven projects

chore(ci): run windows tests against snyk-win.exe

We now require manual approval for each release so that we have better control over new releases.

So that we don't accidently cause a release when modifying our pipelines.

chore(ci): tidy up release job