The output of new versions should be consistent with the Shibuya's in 2.0.1

[chrisli30]

The format of the outputs are reverted back to a dis-organzied version. Please revise them so all files are consistent with the one in,
https://github.com/OAK-Foundation/xcm-demo/blob/release/2.0.1/src/astar/shibuya.js

Expected output format

User Alice turing-dev address: 6AwtFW6sYcQ8RcuAJeXdDKuFtUVXj4xW57ghjYQ5xyciT1yd, shibuya address: ajYMsCKsEAhEvHpeA4XqsfiA9v1CdzZPrCfS6pEfeGHW9j8
Shibuya ID on Turing:  4

1. One-time proxy setup on shibuya ...

a) Add a proxy for Alice If there is none setup on shibuya (paraId:2114) 

Proxy address ZDJA2VoNLGf7TfwUB4bG4kt1jfZSMAkK2s5XTAuYUwFbDpV for paraId: 2114 and proxyType: Any already exists; skipping creation ...

b) Proxy's balance on shibuya is 309.9945 SBY.

2. One-time proxy setup on Turing

a) Add a proxy for Alice If there is none setup on Turing (paraId:2000)

Proxy address 6AriZW88JVhe92iYmEpBusuXpcQDgvixJYHnUUffJ6cAskoG for paraId: 2000 and proxyType: Any already exists; skipping creation ...

b) Proxy's balance on turing-dev is 319.9999 SBY.

3. Execute an XCM from shibuya to schedule a task on turing-dev ...

a). Create a payload to store in Turing's task ...
Encoded call data: 0x120000d43593c715fdd31c61141abd04a99fd6822c8558854ccde39a5684e7a56da27d01000a073048656c6c6f20776f726c6421
Encoded call weight: {"refTime":177297019,"proofSize":4706}

b) Prepare automationPrice.scheduleXcmpTask extrinsic for XCM ...
weight: (6995000000, 0)
Encoded call data: 0xc8041c536869627579612061727468737761700c5455520c534259c7f14e120e6500000000000000000000000003010100411f03010100411f03010100411f2b857121f64f13000000000000000000d0120000d43593c715fdd31c61141abd04a99fd6822c8558854ccde39a5684e7a56da27d01000a073048656c6c6f20776f726c6421ee59452a8949077b123270018a491800
requireWeightAtMost:  { refTime: '995,000,000', proofSize: '0' }

c) Execute the above an XCM from Shibuya to schedule a task on Turing Dev ...
status.type Ready
status.type InBlock
status.type Finalized

At this point if the XCM succeeds, you should see the below events on both chains:

  1. Shibuya

  xcmpQueue.XcmpMessageSent and polkadotXcm.Sent - an XCM is successfully sent from Shibuya to Turing to schedule a task.

  2. Turing Dev

  a) proxy.ProxyExecuted and automationTime.TaskScheduled - the above XCM is received and executed on Turing.

  b) xcmpHandler.XcmTransactedLocally, xcmpQueue.XcmpMessageSent, xcmpHandler.XcmSent and automationTime.XcmpTaskSucceeded - the task is triggered and its payload is sent to Shibuya via XCM.

  3. Shibuya

  proxy.ProxyExecuted and xcmpQueue.Success - the above payload is received and executed.

Listening to TaskScheduled event on Turing chain ...