fix: do not remove supportedVersion key from pallet-xcm

[ashutoshvarma]

Summary

• Update the snapshots
• Keep the supportedVersion storage from pallet-xcm

Why?

With the new XCMv5, the deprecated XCMv2 has been completely removed. Hence any conversion to XCM v2 will result in error.

Previously, to speed-up things we removed the all the keys related to version notification from pallet-xcm, this included the supportedVersion which stored remote locations latest supported xcm version. Hence when sending xcm in the absence of supportedVersion the pallet-xcm convert the outgoing xcm to version stored in SafeXcmVersion.

The SafeXcmVersion is currently set to 2 in all our runtimes, and V2 has been completely removed so this conversion will fail now and thus XCM message couldn't being send

[ashutoshvarma]

In the snapshots, the messageQueue events have different values with new uplift runtime the xcm weights have become slightly more.

- Expected
+ Received

@@ -21,12 +21,12 @@
      "data": {
        "id": "(hash)",
        "origin": "Parent",
        "success": true,
        "weightUsed": {
-         "proofSize": "(rounded 9400)",
+         "proofSize": "(rounded 9300)",
-         "refTime": "(rounded 900000000)",
+         "refTime": "(rounded 890000000)",
        },
      },
      "method": "Processed",
      "section": "messageQueue",
    },

Redacting the the weights to 8 precision would be too much

[ermalkaleci]

Nice! We will need to ignore refTime until upgrade is finished, then we can revert it. It can be done on another PR