[Access] SendAndSubscribeTransactionStatuses should include the transaction result in the response.

[Guitarheroua]

Problem Definition

The SendAndSubscribeTransactionStatuses was implemented for the Access API, but the response of this subscription contains only TX Status, TX ID, and MessageIndex. It would be useful to add TX Result to the response when TX was executed.

Proposed Solution

Add another TX result field to the SendAndSubscribeTransactionStatuses response and retrieve it when TX is executed.

Definition of Done

Update unit and integration tests to ensure that the new field is in place and correct.

[Guitarheroua]

This issue could also be fixed in the scope of this task.

[peterargue]

The SendAndSubscribeTransactionStatuses should have a new field that returns a TransactionResultResponse message. This field should be populated by the server when sending the "executed" response.

A single message should be sent for each of the status in the tx lifecycle, and message should be sent in order:
pending -> finalized -> executed -> sealed [or]
pending -> expired

If the backend runs into a situation where it discovers the tx is finalized and executed in the same run, it should send 2 back-to-back messages, the first for finalization, the second for executed including the result. It should not wait 1 block before sending the executed message. The goal for this endpoint is to provide access to the real time processing of a tx, so we should avoid adding any unnecessary delays.