Update publisherTrustedAlgorithmPublishers and publisherTrustedAlgorithms

[mariacarmina]

Fixes #943 #945 .

Changes proposed in this PR:

• Update publisherTrustedAlgorithmPublishers logic for allowing/denying all addresses
• Update publisherTrustedAlgorithm logic for allowing/denying all algorithm DIDs
• Added tests
• Docs updated here

[bogdanfazakas]

think this is missing this logic

• Add the serviceId field to the object within the publisherTrustedAlgorithms array. to enable searching on both asset id and service id. The structure of the object within publisherTrustedAlgorithms will look as follows:

{
"did": "".
"serviceId": "",
"filesChecksum": "",
"containerSectionChecksum": ""
}

part of #945

[mariacarmina]

think this is missing this logic

• Add the serviceId field to the object within the publisherTrustedAlgorithms array. to enable searching on both asset id and service id. The structure of the object within publisherTrustedAlgorithms will look as follows:

{ "did": "". "serviceId": "", "filesChecksum": "", "containerSectionChecksum": "" }

part of #945

I will comment on the issue regarding the need of serviceId parameter, for now it was not established in the meetings to include serviceId in trusted algo shape. Right now the algorithm can be searched by unique DID, it is a bit unclear described the need to search/filter the access of trusted algorithms by service. Filtering by service can be meaningful when you handle with multiple fixed rates attached to the algorithm, but not sure if it helps for allowing the algorithm to run on a specific dataset (access control).

Thank you!

[giurgiur99]

LGTM