Make vc gen suite configurable

[aljones15]

Removes all cryptosuites from data integrity pushing them out to their respective test projects
the only exception is eddsa-2022 which is maintained for backwards compatibility and should be removed
in a future major release.

Features:

1. changes the verifier test suite to take in a cryptosuite library or instance for test data generation
2. moves deps for cryptosuites to devDeps ensuring that test suites that use this lib don't end up with multiple versions of cryptosuites installed
3. adds VC 2.0 context to documentLoader
4. turns issuedVc and validVc into pure JSON

[BigBlueHat]

Just a wee whitespace tweak request at this point.

[BigBlueHat]

Some tweak requests and some questions.

[BigBlueHat]

Can we store this as a .json file, since that's all it is?

[aljones15]

I made it a parameter to the functionL 09184ae

I am hoping to remove a default key entirely in a MAJOR release as this library really should just throw if you don't pass in a key to this suite.

[BigBlueHat]

I think this reply was to something else, maybe? I don't see sdDoc.js included anywhere (in this code at least), but would still like to see it be stored as JSON if possible.

[aljones15]

sdDoc is now json: ca1a065

There is some pain involved with this. Even node 22's support using module/ es6 imports for json is still experimental: https://nodejs.org/api/esm.html#json-modules

So I have to use createRequire or use node's fs to import json. Using the experimental feature with {type: 'json'} results in eslint breaking as eslint does not support features in the experimental stage. Weirdly, the parser they use esprima does not throw on esprima.tokenize("import foo from './bar.json' with {type: 'json;}");

[BigBlueHat]

Yeah, we do this already to import the other JSON in the test suites. My main goal is to make sure we use "the simplest thing that could possibly work"--i.e. don't use JavaScript when JSON is all that's needed.

[aljones15]

also of note, there is probably a small army of developers working on making es6 import statements work with json and other file types with out having to use with anyways, I moved the key, issuedVc, and validVc all to json here: f772bf8

I will need to check and make sure no test suite was somehow calling on validVc outside of this library (I just began exporting it in this PR so we should be safe). anyways, that should be it.

[BigBlueHat]

Why the timeout increase?

[aljones15]

bbs takes forever.

[BigBlueHat]

Is there a reason these were moved to devDependencies?

[aljones15]

these are no longer required by this library, but are supplied instead by each individual test suite.

[BigBlueHat]

Then why are they still in the dependency list here?

[aljones15]

https://docs.npmjs.com/cli/v10/configuring-npm/package-json#devdependencies

If someone is planning on downloading and using your module in their program, then they probably don't want or need to download and build the external test or documentation framework that you use.

In this case, it's best to map these additional items in a devDependencies object.

The devDeps in this case are for the test project.

[BigBlueHat]

For the tests that test this test project? 😜

[BigBlueHat]

Then why are they still in the dependency list here?

[BigBlueHat]

I think this reply was to something else, maybe? I don't see sdDoc.js included anywhere (in this code at least), but would still like to see it be stored as JSON if possible.

[BigBlueHat]

This looks good to go. I'd love those long lived FIXME comments taken out, but we can do that later/elsewhere if you need to get this merged sooner than later.

Thanks!