feat(core-api): add createIsJwsGeneralTypeGuard, createAjvTypeGuard<T>

[petermetz]

1. createAjvTypeGuard() is the lower level utility which can be used
   to construct the more convenient, higher level type predicates/type guards
   such as createIsJwsGeneralTypeGuard() which uses createAjvTypeGuard
   under the hood.
2. This commit is also meant to be establishing a larger, more generic
   pattern of us being able to create type guards out of the Open API specs
   in a convenient way instead of having to write the validation code by hand.

An example usage of the new createAjvTypeGuard() utility is the
createIsJwsGeneralTypeGuard() function itself.

An example usage of the new createIsJwsGeneralTypeGuard() can be found
in packages/cactus-plugin-consortium-manual/src/main/typescript/plugin-consortium-manual.ts

The code documentation contains examples as well for maximum discoverabilty
and I'll also include it here:

import { JWSGeneral } from "@hyperledger/cactus-core-api";
import { createIsJwsGeneralTypeGuard } from "@hyperledger/cactus-core-api";

export class PluginConsortiumManual {
  private readonly isJwsGeneral: (x: unknown) => x is JWSGeneral;

  constructor() {
    // Creating the type-guard function is relatively costly due to the Ajv schema
    // compilation that needs to happen as part of it so it is good practice to
    // cache the type-guard function as much as possible, for examle by adding it
    // as a class member on a long-lived object such as a plugin instance which is
    // expected to match the life-cycle of the API server NodeJS process itself.
    // The specific anti-pattern would be to create a new type-guard function
    // for each request received by a plugin as this would affect performance
    // negatively.
    this.isJwsGeneral = createIsJwsGeneralTypeGuard();
  }

  public async getNodeJws(): Promise<JWSGeneral> {
    // rest of the implementation that produces a JWS ...
    const jws = await joseGeneralSign.sign();

    if (!this.isJwsGeneral(jws)) {
      throw new TypeError("Jose GeneralSign.sign() gave non-JWSGeneral type");
    }
    return jws;
  }
}

Relevant discussion took place here:
#3471 (comment)

Signed-off-by: Peter Somogyvari peter.somogyvari@accenture.com

Pull Request Requirements

• Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

[petermetz]

cc: @RafaelAPB @eduv09 Please take a look at how the casting to JWSGeneral can be eliminated once this PR gets merged (look at the diff for the file packages/cactus-plugin-consortium-manual/src/main/typescript/plugin-consortium-manual.ts in this PR to see what I mean exactly)

[jagpreetsinghsasan]

LGTM

[RafaelAPB]

The cast LGTM, thanks @petermetz.

[petermetz]

The cast LGTM, thanks @petermetz.

@RafaelAPB You got it! Any other casting/error handling related stuff you need help with just let me know! It is important for production deployments to have these nailed down and I want to help as much as I can!