TezosXPoC/Kernel: Gateways create a CrossRuntimeContext to call the foreign runtimes.

What

Add CrossRuntimeContext in the invocation part of the RuntimeInterface and thread it through the code.

Preparatory work for L2-851 and L2-852

Why

The VM need BlockConstants to be invoked. The informations required are available in the gateways but need to be passed on to the VM.

How

This has already been solved for generating the alias (the EthereumRuntime use it's VM to generate_alias ) by creating AliasCreationContext. So we rename it in CrossRuntimeCOntext and reuse the structure for the RuntimeInterface::call (and the Registry::bridge that calls it).

Manually testing the MR

Pure refacto, no logic yet (argument is ignored until we invoke the VMs) so no dedicated test.

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR