Print out XCM configs of both source and dest chains in the beginning

[chrisli30]

Motivation

We should print out the value of

instructionWeight
WEIGHT_REF_TIME_PER_SECOND
and feePerSecond

in the very beginning for the chains and assets used in the program. That way it will be eaiser for developers to read logs.

[chrisli30]

Some xcm configs are read on-chain, but there should be interfaces in adapter that will allow us to call to retrieve those configs. @imstar15 the goal is to call adapter functions to retrieve and print out xcm configs in the beginning of every xcm-demo. Let’s add that line in arthswap price demo first.

[chrisli30]

Moonbeam’s instructionWeight varies across instruction type, and is configured in @oak-network/config, but feePerSecond is calculated by its chain’s PRC with an actual weight value.

The total xcm weight can also be retrieved by overallWeight - payload’s weight