Feature/14/14 Registration Service JWS authentication

[algattik]

What this PR changes/adds

Access to the Registration Service API is authenticated with JWS. Adapted accordingly:

• the Registration Service CLI call in the deployment pipeline
• the federated Directory implementation in EDC, for retrieving the participants list

Why it does that

Authentication ensures that only actors who can assert their control of a did:web identifier can register that identifier as a dataspace participant.

Further notes

• Updated Registration service commit dependency for the required JWS support
• Updated Registration service URLs given new port and URL mapping (https://github.com/agera-edc/RegistrationService/pull/14)
• Updated EDC version because of a required fix (#1575)
• The curl command to check registration service is up doesn't work anymore, since a JWS is required. I've remove the curl command and let the workflow fail when deploying participants. Other options could be pursued in follow-up issues, e.g.:
  • adapt the curl command to succeed if a 401 is returned and fail otherwise
  • use the CLI client list participants command with the authority key
  • use az container show to check state=running (based on internal health check), waiting if necessary
  • use az container exec to run curl within the container, waiting if necessary
  • expose port 8181
  • use Terratest
• Also changed workflow trigger to run on all PRs, not only to main branch, to facilitate downstream fork process.

Linked Issue(s)

https://github.com/agera-edc/MinimumViableDataspace/issues/14

Checklist

• [ ] added appropriate tests?
• [ ] performed checkstyle check locally?
• [ ] added/updated copyright headers?
• [ ] documented public classes/methods?
• [ ] added/updated relevant documentation?
• [ ] added relevant details to the changelog? (skip with label no-changelog)
• [ ] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)