Feat: update asset endpoints

[OlfaBensoussia]

Description

With the EDC milestone 9 release, there were some changes when it comes to the asset related entities.
This PR addresses all of them but doesn't add the new asset endpoints.
To sum it up, we:

• Added a new Context object
• Updated the CreateResult object
• Fixed the wrong endpoint that was used to get an asset's data address
• Updated Asset objects and added new ones
• Updated tests
• Updated some utilities.

How to test it

• Asset related tests should be passing successfully

---

Approach

• To understand why those changes had to be made, we checked the management API and made use of the open source POSTMAN collection published by the Tractus-x team
• Those are some screenshots from my local postman to give more context:

1. Creating a new asset: POST {{ConnectorManagementURL}}/v2/assets

2. Getting the list of assets: POST {{ConnectorManagementURL}}/v2/assets/request

3. Getting an asset: GET {{ConnectorManagementURL}}/v2/assets/{{AssetId}}

4. Getting an asset's data address: GET {{ConnectorManagementURL}}/v2/assets/{{AssetId}}/dataaddress

Open Questions and Pre-Merge TODOs

• Update readme examples
• Check if we have added all of the asset's primitive types or not. We already have description, name and contenttype. I remember we have more than that but I will need to go through the base code to get them.

[OlfaBensoussia]

I tagged @fdionisi as the main reviewer to validate this PR from an approach and coding perspective.
I am tagging @NabilHouidi @AhmedGrati and @Nazdroth to help validate this from a functional POV considering that your team is working on the migration too.

[fdionisi]

Is there something we should do to enable testing?
Have we considered already using some json-ld package to avoid working on the types ourselves?

[OlfaBensoussia]

Is there something we should do to enable testing? Have we considered already using some json-ld package to avoid working on the types ourselves?

@fdionisi thank you so much for taking the time to review this.

• By enabling testing, do you mean fixing the failing ones or something else?
• Before making those changes, I had a look at the jsonld package to see if it can be useful to use here. After consideration, it seemed to me that the package is only useful if you want to make some manipulations [compacting, flattening..] on the json objects. In our case, I didn't feel like there will an added value for using it, especially that we're not actively making changes on the objects.

[fdionisi]

@OlfaBensoussia, sorry for my poor communication. I meant that we should make tests pass, but now we are on the latest version of the connector. We should try land #35 first and then use the docker image to endure correct functionality on this PR. I don't think we'll be developing anymore for milestone-8 (except for #20, for now). Hence, it should be find to proceed

[fdionisi]

• Before making those changes, I had a look at the jsonld package to see if it can be useful to use here. After consideration, it seemed to me that the package is only useful if you want to make some manipulations [compacting, flattening..] on the json objects. In our case, I didn't feel like there will an added value for using it, especially that we're not actively making changes on the objects.

I hear you. It makes sense to me for now, but I would like to explore the possibility of using a json-ld-aware library to perform input validation - if the format is not correct, then it's not worth bothering the backend in my opinion. Let's keep this exploration for later.

[OlfaBensoussia]

@ndr-brt I tried to fix most of the failing tests, remove any hardcoded values and update most of the entities. As far as it concerns the management tests, they are all now passing except the ones that rely on the function waitForNegotiationState.
I have a gut feeling that there is an issue with the Negotiation states in general. As an example, canceling a contract negotiation doesn't automatically change the state to ERROR, it stays as TERMINATING for a while first.
I still need your help in understanding that part and fixing the remaining failing ones. Once we do that, we should be good to consider that we have the Lib compatible with v0.1+

[ndr-brt]

@ndr-brt I tried to fix most of the failing tests, remove any hardcoded values and update most of the entities. As far as it concerns the management tests, they are all now passing except the ones that rely on the function waitForNegotiationState. I have a gut feeling that there is an issue with the Negotiation states in general. As an example, canceling a contract negotiation doesn't automatically change the state to ERROR, it stays as TERMINATING for a while first. I still need your help in understanding that part and fixing the remaining failing ones. Once we do that, we should be good to consider that we have the Lib compatible with v0.1+

TERMINATING it is correct, the state machine changed a lot since then. Please note that the /cancel endpoint has been deprecated as well, replaced by /terminate.

I will take a look at it, great work so far. 🙌

[ndr-brt]

@OlfaBensoussia I fixed stuff here and there, the CI is green. I'll propose to merge this into my PR and then I will fixup some cosmetics that needs to be in place before release, let me know.

EDIT: it works on my computer but not on github 😆

[OlfaBensoussia]

@ndr-brt Thank you for the clarifications. I will merge this and we can fix the rest of the tests on the original branch