Resources must have a participantId property

[paullatzelsperger]

Feature Request

All resources in IdentityHub must have a property participantId by which they can be associated with the ParticipantContext that owns them.
Semantically, this is similar to an SQL foreign key relation, although in practice it will only be a loosely coupled business key.

Which Areas Would Be Affected?

DidDocumentResource, VerifiableCredentialResource, KeyPairResource

Why Is the Feature Desired?

to separate participant boundaries, e.g. when validating API requests or when determining affected resources after a modifying operation

Solution Proposal

Add a property participantId to every resource and initialize it during object creation.