Function signatures for MsgExecuteContract inconsistent with Terra.js

[przmyst]

Update documentation to specify that cosmes MsgExecuteContract takes an Object with sender, contract, msg, and funds properties vs 4 arguments with Terra.js MsgExecuteContract.

      const msgs = [
       //Does not work as expected with cosmes
        new MsgExecuteContract(
          'terra1u9k8h9e9u9jg7yq50myt8d20hhmwc0wyznf4yy',
          'terra136cqzlps72yma3z8pdlw43nnwvf6d2cn6jcf9a4zxtwmhx4hka7sw7ymdp',
          {
            swap: {
              offer_asset: {
                info: {
                  native_token: {
                    denom: 'uluna'
                  }
                },
                amount: 2000000000
              }
            }
          },
          { uluna: 2000000000}
        ),
       //Works with cosmes
        new MsgExecuteContract({
          sender: 'terra1u9k8h9e9u9jg7yq50myt8d20hhmwc0wyznf4yy',
          contract: 'terra136cqzlps72yma3z8pdlw43nnwvf6d2cn6jcf9a4zxtwmhx4hka7sw7ymdp',
          msg: {
            swap: {
              offer_asset: {
                info: {
                  native_token: {
                    denom: 'uluna'
                  }
                },
                amount: 2000000000
              },
            }
          },
          funds: [
            new Coin('uluna', 2000000000).toAmino()
          ]
        })
      ]

[AaronCQL]

Closing in favour of #3. This library does indeed have a different function signature to both cosmjs and featherjs.