This is a proposal to activate the bridge pallet on Moonriver, a required step toward the ultimate goal of enabling a trustless, native bridge between Moonriver and Moonbeam.

The proposal is actually a batch of several actions including:

* Register foreign assets on Moonriver
* Set a *temporary* owner on the “Bridge Grandpa” and “Bridge Messages” pallets which can later be used to initialize them.

The bridge will not be active until the entire process is completed.  See below for details.&#x20;

Please see [the forum post](https://forum.moonbeam.network/t/proposal-mr86-prepare-moonriver-for-the-activation-of-the-moonbeam-moonriver-bridge/2232) for more details.

Send a batch of dispatch calls and atomically execute them.
The whole transaction will rollback and fail if any of the calls failed.

May be called from any origin except `None`.

- `calls`: The calls to be dispatched from the same origin. The number of call must not
  exceed the constant: `batched_calls_limit` (available in constant metadata).

If origin is root then the calls are dispatched without checking origin filter. (This
includes bypassing `frame_system::Config::BaseCallFilter`).

## Complexity
- O(C) where C is the number of calls to be batched.

#86 Prepare Moonriver for the activation of the Moonbeam <> Moonriver Bridge