fix(MultiSig)!: change interface and substitute adaptive_address for autonomy

[LycrusHamster]

What type of PR is this?

fix(multi-sig)!: change interface and substitute adaptive_address for autonomy

BREAKING CHANGE: the interface is changed and affect on all sdk/clients

What this PR does / why we need it:

due to the bech32 format, the adaptive address is not suitable.

so we add 'autonomy' field.

B.T.W. change the UpdateAccountPayload to make it non-ambigious
B.T.W. change the genesis payload to remove ambiguity.

Docs is here
https://github.com/HuobiGroup/huobi-chain-docs/pull/8

Java sdk:
nervosnetwork/muta-sdk-java#24

due to 2 different iteration, the pr of java sdk has been merged. This is a exclusion this time

Js sdk:

nervosnetwork/muta-sdk-js#23

[yejiayu]

/cc @KaoImin

[KaoImin]

I think the type of this PR is refactor rather than fix.

[yejiayu]

Will this PR have BRACKING_CHANGE?
Why does not add ! to the title?
Does the toolchain need to adapt?

@LycrusHamster @homura

[LycrusHamster]

Will this PR have BRACKING_CHANGE?
Why does not add ! to the title?
Does the toolchain need to adapt?

@LycrusHamster @homura

Yes, now question mark has been added and BREAKING CHANGE have been explicitly add in the commit msg\

Yes, already dispatch sdk modification to java sdk and js sdk

[yejiayu]

/hold

Wait SDK adaption

[yejiayu]

/hold cancel

[yejiayu]

/lgtm

[LycrusHamster]

/approve

[muta-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LycrusHamster, yejiayu

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [LycrusHamster,yejiayu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment