Test invocations feedback

[carpawell]

Is your feature request related to a problem? Please describe.

I'm always frustrated when I do not know how test invocation finished in test VM. Especially when debugging things.

Describe the solution you'd like

1. Add runtime logs in test invocation's response.
2. In logs on the server side, make it clear when runtime.Log is about an accepted block already on chain and, on the contrary, when it is only a test invocation.

Describe alternatives you've considered

-

Additional context

I was debugging the problem of skipped transactions (nspcc-dev/neofs-node@04686e7) and spent time finding out why I see logs about transactions being executed but no outcome could be seen in the chain. Test invocations were logged, and I took it as true block inclusion but nothing was accepted.

[roman-khimov]

Add runtime logs in test invocation's response.

A protocol extension. But I guess everyone wants it in fact.