ci: replace verification repository

[JamieMagee]

This PR migrates from using a private repository, componendetection-verification, and moves verification tests into this repo. The verification tests have been rewritten to be minimal projects that exercise all functionality of a detector.

The current verification tests are expected to fail in this PR as the most recent snapshots are for the old verification projects.

Closes #44

[github-actions]

👋 Hi! It looks like you modified some files in the Detectors folder.
You may need to bump the detector versions if any of the following scenarios apply:

• The detector detects more or fewer components than before
• The detector generates different parent/child graph relationships than before
• The detector generates different devDependencies values than before

If none of the above scenarios apply, feel free to ignore this comment 🙂

[jcfiorenzano]

The verification repo for pip has to have the dependencies frozen:
These are the steps that need to be followed for pip

Instead you want to:

Create a new virtual env (see [here](https://packaging.python.org/guides/installing-using-pip-and-virtual-environments/))
Activate the virtual env
pip install -r requirements.txt
pip freeze
Pip freeze will write out to a console, so you can either pipe to a requirements.txt.

[jcfiorenzano]

I would also add the steps to the Contribution (or README) about how to add a new verification repo

[JamieMagee]

After discussing with @jcfiorenzano, I've decided to create some synthetic verification/integration/e2e tests instead. Checking out other repositories is flaky, and overall not a reliable method for this style of test.

[jcfiorenzano]

There is a file ivi.jar at the repo root. Is that intendend?

[jcfiorenzano]

I would add a note in this document https://github.com/microsoft/component-detection/blob/main/docs/creating-a-new-detector.md. Explaining how and where to add a new verification repo.

[JamieMagee]

There is a file ivi.jar at the repo root. Is that intendend?

Good catch. It's left over from testing locally

I would add a note in this document main/docs/creating-a-new-detector.md. Explaining how and where to add a new verification repo.

Will do!