add: tx.origin and msg.sender to the remote zEVM omni-chain contract call

[brewmaster012]

Synopsis
To be able to be called remoted on an foreign chain, the zEVM contract must conform to this interface

    function onCrossChainCall(address zrc20, uint256 amount, bytes calldata message) external;

This interface does not provide any information as to who the remote caller address is (analogous to Ethereum tx.origin and msg.sender).

Propose to add a context field to the interface so that zEVM omni-chain contract can obtain information as to who remotely invoked the contract.

    function onCrossChainCall(Context ctx, address zrc20, uint256 amount, bytes calldata message) external;

where context is a struct

struct Context {
        bytes origin; // similar to tx.origin, bytes becasue it could be from bitcoin
        address sender; // similar to msg.sender; empty if on bitcoin network 
        uint64 chainID; // foreign chain id from which this contract is remotely called
    }

Affected components:
SystemContract: change according to the interface change; needs to be redeployed on athens3;
Inbound Transaction Voter: Needs to supply tx.origin and msg.sender information.
zEVM I/O contracts: needs to change onCrossChainCall interface and re-deployed.

[lumtis]

Is it the same task as #828?

[brewmaster012]

Is it the same task as #828?

yes let's close #828