Build error for kbs-types definition about kbs HOT 1 CLOSED

Although we can fix this error temporarily by specifying a rev, it is important to keep consistent the code with the document, s.t. synchronize virtee and confidential-containers community.

Also, there is some observations from my side:

Now we use JWK in a format as defined in https://github.com/confidential-containers/kbs/blob/main/docs/kbs_attestation_protocol.md#public-key

{
    "kty": "$key_type",
    "alg": "$key_algorithm",
    "k": "public_key"
}

However the JWK defined in RFC7517 https://www.rfc-editor.org/rfc/rfc7517# does not have the field k different member fields due to alg.

Now we use RSA pkcs1v15 padding / key length = 2048bit as the public algorithm. To follow the RFC it might look like the following?

{
    "kty": "RSA", // https://www.rfc-editor.org/rfc/rfc7518#section-6.1
    "alg": "RS256", // https://www.rfc-editor.org/rfc/rfc7518#section-3.1
    "n": "<base64-encoded n parameter in RSA public key>" // https://www.rfc-editor.org/rfc/rfc7518#section-6.3.1.1
    "e": "<base64-encoded e parameter in RSA public key>" // https://www.rfc-editor.org/rfc/rfc7518#section-6.3.1.2
}

although it is still not a problem as AA & AS logic are all controlled by us so it can pass CI, we should think about "normalize" the definition (including the key type selection) after v0.5.0? cc @sameo @jialez0

from kbs.