Add pallet-xcm precompile to Moonbeam and Moonriver (transfer_assets_using_type_and_then extrinsic support)

[Agusrodri]

What does it do?

This PR adds support for pallet-xcm precompile in both Moonbeam and Moonriver runtimes.

It also updates the moonkit's pin to include the most recent changes of the precompile, related to the new feature of using transfer_assets_using_type_and_then extrinsic through the precompile.

Related Moonkit PR

• Add support for transfer_assets_using_type_and_then extrinsic in pallet-xcm precompile Moonsong-Labs/moonkit#54

[github-actions]

WASM runtime size check:

Compared to target branch

Moonbase runtime: 2292 KB (no changes) ✅

Moonbeam runtime: 2268 KB (no changes) ✅

Moonriver runtime: 2260 KB (no changes) ✅

Compared to latest release (runtime-3200)

Moonbase runtime: 2292 KB (+332 KB compared to latest release) ⚠️

Moonbeam runtime: 2268 KB (+344 KB compared to latest release) ⚠️

Moonriver runtime: 2260 KB (+336 KB compared to latest release) ⚠️

[github-actions]

Coverage Report

@@                         Coverage Diff                          @@
##           master   agustin-xcm-transfer-assets-using     +/-   ##
====================================================================
  Coverage   79.12%                              79.12%   0.00%     
  Files         303                                 303             
+ Lines       88015                               88017      +2     
====================================================================
  Hits        69637                               69637             
+ Misses      18378                               18380      +2     

Files Changed	Coverage
/runtime/moonbeam/src/lib.rs	46.62% (-0.08%)	🔽
/runtime/moonriver/src/lib.rs	46.85% (-0.07%)	🔽

Coverage generated Tue Oct 8 17:59:03 UTC 2024

[RomarQ]

The changes look good to me

[RomarQ]

@Agusrodri Do we need to change any benchmarks?

[Agusrodri]

@Agusrodri Do we need to change any benchmarks?

@RomarQ I don't think we need to change benchmarks itself. Although, I noticed that we don't have weights for transfer_assets_using_type_and_then pallet-xcm extrinsic. Should we generate them in this PR or shall we wait for the benchmarks PR that is done every release?

[RomarQ]

@Agusrodri Do we need to change any benchmarks?

@RomarQ I don't think we need to change benchmarks itself. Although, I noticed that we don't have weights for transfer_assets_using_type_and_then pallet-xcm extrinsic. Should we generate them in this PR or shall we wait for the benchmarks PR that is done every release?

transfer_assets_using_type_and_then uses weights from transfer_assets