IMN 538 - Fix user info fetch during contract creation

[MalpenZibo]

Closes IMN-538

From scala counterpart pagopa/interop-be-agreement-process#263

[ecamellini]

@MalpenZibo Does this apply only to this getSubmissionInfo case or also to the getActivationInfo below?
If it applies also to that case, maybe you could move this logic from here into the retrieveUser, which is called by both functions

[galales]

it can be applied just to submission info.
The submission can be performed only by the consumer, and we can safely take the details from it.

The activation can be done both by consumer and by producer, but in both cases the getActivationInfo is called by the user who also activated the agreement. This is why we can take the info starting from the context (of the jwt)

[ecamellini]

Left a comment (the same question applies to the solution being applied to Scala, so maybe it needs also to be clarified on that side)

[ecamellini]

I double checked, the same question I left here applies to the fix on the Scala code cc @nttdata-rtorsoli & @galales / @beetlecrunch

[galales]

it can be applied just to submission info.
The submission can be performed only by the consumer, and we can safely take the details from it.

The activation can be done both by consumer and by producer, but in both cases the getActivationInfo is called by the user who also activated the agreement. This is why we can take the info starting from the context (of the jwt)