The next [runtime upgrade v0.4.0](https://zeitgeist.subsquare.io/council/motions/34) requires `polkadotXcm.safeXcmVersion` to be configured properly to be able to send XCM, as `pallet-xcm` uses the storage instead of a hard coded value from v0.4.0 onward.

Right now XCMv2 is deployed. The message format V1 is the oldest supported version, V2 is the current version. With v0.4.0, XCMv3 is deployed. The message format V1 will be deprecated, V2 will be the safe default and V3 will be the most recent version.

⚠ Not configuring this value before deployment of v0.4.0 results in the inability to send XCMs. 

 Approve a proposal. At a later time, the proposal will be allocated to the beneficiary
 and the original deposit will be returned.

 May only be called from `T::ApproveOrigin`.

 # <weight>
 - Complexity: O(1).
 - DbReads: `Proposals`, `Approvals`
 - DbWrite: `Approvals`
 # </weight>

Problem Statement & Audience:
- The problem is ensuring the availability and support of the Moonbeam Multisig interface for the Moonbeam community, including incidents, errors, and updates.
- The intended audience is the Moonbeam community, including users, DAOs, DeFi projects, and developers.

Significance:
- Moonbeam Multisig is a trusted platform for storing digital assets and interacting with smart contracts, supporting TVL growth and benefiting the Moonbeam community.

Proposed Solution:
- Regular updates and maintenance of the Moonbeam Multisig instance, including frontend and backend improvements, smart contract updates, and the addition of new functionalities.

Expected Outcomes:
- Continued availability and support of the Moonbeam Multisig interface.
- Increased trust and adoption of Moonbeam Multisig by the community.
- Improved user experience and functionality of the Moonbeam Multisig platform.

#35 Set safe default XCM version to 2