Check lane id of incoming messages

[svyatonik]

slightly related to https://github.com/paritytech/srlabs_findings/issues/142

We shall verify lane of incoming messages - something that we already had before, but lost now. With XCM bridge it means:

• when we are receiving messages from unsupported lane (e.g. in RBH<>WBH we now only support lane [0, 0, 0, 1] for messages between *mint/*mine chains) - we shall return error from verify_messages_proof if proof contains messages from some other lane. Now this is some static check, but later we'll probably need to maintain map of LaneId => (XcmSource, XcmDestination);
• @bkontur can we verify that the message is actually sent by the proper source parachain and that it'll be routed to the proper target parachain. For example - when dispatching message that has came by lane [0, 0, 0, 1] to WBH, we want to ensure that it has been actually sent by Rockime2 and is going to Wockmint. Can we do that, or is it handled somewhere already? WDYT about that?

@bkontur @serban300 Can you, guys, please, tackle this?

[bkontur]

@svyatonik
I will take it,
because for pallet-bridge-assets-transfer for moving assets, I have PoC for some mapping on-chain for bridge configuration with simple CRUD operations (add_bridge_config, update_bridge_config, remove_bridge_config) with let _ = ensure_root(origin)?; that could be triggered just by governance-like

and next week on CGP retreat, I would like to disccuss this and other stuff with Joe, so after that, I would be able to align all similar configurations and do it in one way

[EmmanuellNorbertTulbure]

@bkontur to recheck it

[EmmanuellNorbertTulbure]

@bkontur to recheck it

[bkontur]

@svyatonik
to this discussion: zdave-parity/polkadot-bulletin-chain#28 (comment)
I think for V1 we dont check sender vs lane:

MessagesPallet::<H::Runtime, H::MessagesInstance>::send_message(sender_and_lane.lane, blob)

the only usage of SenderAndLane.location I see in LocalXcmQueueManager,
I am going to add some simple test to BridgeHubRococo runtime,
and I will add simple validation for MessageExporter because impl ExportXcm::validate should have all parameters