Credential status implementation for LtoStatusRegistry2023

[jasny]

Add an implementation for the Veramo credential-status library to support LtoStatusRegistry2023.

{
  "id": "GKot5hBsd81kMupNCXHaqbhv3huEbxAFMLnpcX2hniwn",
  "statements": [
    {
      "type": "issue",
      "timestamp": 1688781798500000,
      "signer": {
        "type": "Ed25519VerificationKey2020",
        "publicKeyMultibase": "zH3C2AVvLMv6gmMNam3uVAjZpfkcJCwDwnZn6z3wXmqPV"
      }
    },
    {
      "type": "dispute",
      "timestamp": 1688781798600000,
      "signer": {
        "type": "Ed25519VerificationKey2020",
        "publicKeyMultibase": "zGL293fxZ2uVG6KEtyJ1dKAfXJBMR2264jHivbhN5zpfD"
      },
      "reason": "Credentials compromised"
    },
    {
      "type": "suspend",
      "timestamp": 1688781798700000,
      "signer": {
        "type": "Ed25519VerificationKey2020",
        "publicKeyMultibase": "zH3C2AVvLMv6gmMNam3uVAjZpfkcJCwDwnZn6z3wXmqPV"
      },
      "reason": "Credentials compromised"
    },
    {
      "type": "revoke",
      "timestamp": 1688781798800000,
      "signer": {
        "type": "Ed25519VerificationKey2020",
        "publicKeyMultibase": "zH3C2AVvLMv6gmMNam3uVAjZpfkcJCwDwnZn6z3wXmqPV"
      }
    }    
  }
}

Disputes should be matched against a trust network.

[jasny]

See ltonetwork/indexer#205

[jasny]

Implement ICredentialStatusVerifier in the credential plugin, rather than using credential-status. We might need to change this in the future if there's a more general approach by veramo.