TPM does not always use correlation ID in messages

[ronjaquensel]

Bug Report

Describe the Bug

When sending a message regarding a TransferProcess (e.g. for termination), the TransferProcessManager does not always use the same ID. For outgoing messages regarding a process, the process's correlation ID should be used, as this is shared between the two parties. For e.g. sending a TransferStartMessage, the correct ID is used:

var message = TransferStartMessage.Builder.newInstance()
                 .processId(process.getCorrelationId())

but in case of termination and completion, the process ID is used (which, if the message is sent by the provider, is not known to the consumer):

var message = TransferTerminationMessage.Builder.newInstance()
                ...
                .processId(process.getId())

This causes an error on the counter-party side, as the message can not be correlated to an existing process.

Expected Behavior

Each message regarding a TransferProcess contains an ID known to the counter-party.

Observed Behavior

Some messages contain an ID that is not known to the counter-party.

Possible Implementation

Set the process.getCorrelationId() for the processId on all messages.