GetComputeStatus directCommand and GET /compute have different results for same jobId

[paulo-ocean]

For the same jobId the routes have different results (and both make use of getComputeStatus command)
with directCommand

using /compute endpoint

[paulo-ocean]

Actually, the issue is with param agreementId, the 0x prefix is getting stripped out, when using the legacy route., which eventually leads to a mismatch if this field is used on the query

UPDATE: This is actually happening on ocean SDK computeStatus call done from the CLI

let url = `?consumerAddress=${consumerAddress}`
    url += (agreementId && `&agreementId=${this.noZeroX(agreementId)}`) || ''
    url += (jobId && `&jobId=${jobId}`) || ''

(the noZeroX call )
Not really sure why this was done like this, but better not touch the SDK atm, for backward compatibility... and just add the prefix if missing on Ocean Node side

[alexcos20]

Not really sure why this was done like this, but better not touch the SDK atm, for backward compatibility

It was causing issues on provider, we can remove this in SDK for release 4

[paulo-ocean]

Not really sure why this was done like this, but better not touch the SDK atm, for backward compatibility

It was causing issues on provider, we can remove this in SDK for release 4

ok, thanks.. will create a PR on the SDK as well for that

[paulo-ocean]

closed on #777