Feat: adding Proof Configuration to Signature

[koptan]

Description

PR to include the proof configuration in the final hash during the process of creating and verifying the proof.

Therefore, the verification process should fail if any values in the Proof Configuration attributes change.

This PR should fix #34, also it's merge #38

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• [x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• [x] Copyright and license header are present on all affected files

[koptan]

@DominikPinsel @matgnt @borisrizov-zf @bjoern-arnold, please for your review.

[matgnt]

I would leave this to the others to review. I'm not a Java developer and don't know the libraries internal structure.

[borisrizov-zf]

@koptan you should rebase, because of #44

[koptan]

@borisrizov-zf Rebase is done, you can merge it 👍

[borisrizov-zf]

@koptan Hi, still many more files have the docs deleted, and the copyright year is not 2024. I haven't marked them explicitly, due to the sheer quantity of files. Please review them and fix these issues, before I can continue.

[borisrizov-zf]

@koptan can you point me in the right direction about the following:

verification method can be either a multibase string or a map, but I cannot see where transformation is taking place. The interface which binds these seems to be missing the option to easily extend to something like publicKeyJWK with an EC cipher. Am I missing something?

[koptan]

@borisrizov-zf transformation is happening in TransformedLinkedData, we accept any JsonLD object as parameter.

[borisrizov-zf]

@koptan Hi, the branch needs rebasing, you're out of sync with main.