Allow custom kid to be set in JWS

[PhilippGackstatter]

Description of change

• Allow custom kid to be set in JWS.
• Allow a custom DID Url to be passed to the verification because the assumption that JWS kid == method ID does not always hold.
• Remove leftover crits parameter in Wasm bindings that was removed some time ago on the Rust side.
• Add new Timstamp() constructor, so this does not return a null pointer.
• Add tests for parsing the option types.
• Set the kid of a newly generated JWK to its SHA256 base64-encoded thumbprint, as recommended by did-core:

  • It is RECOMMENDED that JWK kid values are set to the public key fingerprint.
    https://www.w3.org/TR/did-core/#dfn-publickeyjwk

Links to any relevant issues

part of #1103

Type of change

Add an x to the boxes that are relevant to your changes.

• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How the change has been tested

Added new tests.

Change checklist

Add an x to the boxes that are relevant to your changes.

• I have followed the contribution guidelines for this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[abdulmth]

Looks good to me, maybe it would be worth it to add the same Rust test to JS, maybe also test the case when kid isn't set if not tested somewhere else.