[BUG] retrieveTable shows messages from commits running in parallel

[JoernBerkefeld]

events should be filtered by job execution but apparently, when somebody executes a commit and you click on refresh shortly after / similar time then you see the commit progress messages in your refreshing page

[JoernBerkefeld]

from @nrabe-copado :

Here, in line 333
https://github.com/Accenture/sfmc-devtools-copado/blob/master/force-app/main/default/lwc/mcdo_RetrieveTable/mcdo_RetrieveTable.js#L333

we needed to filter by the jobId, skipping events that are not related to the current job execution:

if(stepStatus.externalJobId !== jobExecutionId) {
    return;
}

[JoernBerkefeld]

needs to be re-opend because the original solution didn't work
as of now, "externalJobId" does not include the job execution id in the event:

however, result id is present in the copado__Topic_Uri__c:

maybe we can fetch that via Apex by jumping from the job execution record, to the (one and only) step and finally to the Results record that was last created, assuming that will be ours...?

[JoernBerkefeld]

as of now we are showing all messages in the event channel, which can lead to the retrieveTable page showing parallel running commit or deploys.
we will need to write an apex getter based on having the job execution id that returns either the result id or the job id.
with that, we could then use response.data.payload.copado__Topic_Uri__c which, for updates always has this format:

"/events/copado/v1/step-monitor/"+ resulted

mcdo_RetrieveTable.js > subscribeToCompletionEvent() needs to be updated with that filter