Manage XCM through maintenance mode filters

[Agusrodri]

This PR adds the possibility of managing XCM functionalities through maintenance mode filters.

The following changes were applied to frontier and simple templates, and also to the dancebox runtime:

• MaintenanceFilter will forbid any call to polkadotXcm pallet.

• xcm-support feature was added to pallet-maintenance-mode, alongside with the custom implementations of XcmExecutionManager, NormalDmpHandler and MaintenanceDmpHandler types.

[github-actions]

Master coverage: 72.05%
Coverage generated "Fri Sep 15 13:09:27 UTC 2023":
https://d3gkbsry1ehhqi.cloudfront.net/tanssi-coverage/pulls/243/index.html
Pull coverage: 71.89%

[girazoki]

I am starting to think we should move this into xcm-pritmitives

[Agusrodri]

TODO: add tests for DMP and general XCM messages in maintenance mode.

Edit: the XCM queue works as expected (after disabling maintenance mode the queued message is automatically executed in the corresponding block).

On the other hand, that is not the case with DMP queue, which is failing only on frontier template (the queued message is not being automatically executed after disabling maintenance mode). I'm investigating the issue.

Second edit: (solved)

---

Explanation of the problem

The issue was related to fixed XCM weights and their impact inside the Configuration storage present in DmpQueue pallet.

The ConfigData struct that is saved in this storage, owns a field called max_individual, that represents the maximum amount of weight any individual message coming by DMP may consume during its execution. By default, this field has a related proof_size of 64KB, which conflicts with the fixed size of proof_size for XCM execution (also 64KB).

Due to this conflict, the incoming DMP message is put inside the Overweight queue and is not properly queued in the normal queue for its later execution.

To solve this, a proper solution would be to add a extrinsic to the DmpQueue pallet that allows to change the value inside max_individual field. Meanwhile, we will opt in to add a function inside tests that allows to change the value of max_individual as desired, but the problem will still be there for big XCM messages until we have an upstream solution in DmpQueue pallet.

[girazoki]

@Agusrodri can you merge master in? Also we can merge as is but I will create an issue to move these into their proper primitives crates in moonkit