CBOR map order for named fields in protocol v1.1.0

[Alexey-N-Chernyshov]

Protocols ask/mk/status CBOR encoding don't meet Core CBOR determenistic encoding requirements. The order of keys in the map is as it is defined in the code (for example). The problem is that different order of CBOR map produces different hash that is used in message signatures, so other implementations have to support the non cacnonical order.
I suggest add map keys sorting in canonical order for MarshalCBOR.

[rvagg]

See also whyrusleeping/cbor-gen#42 (followed by whyrusleeping/cbor-gen#56) where I've tried to push this before.

It's not the Core CBOR standard we should be following, but the DAG-CBOR standard where we're very explicit about this: https://ipld.io/specs/codecs/dag-cbor/spec/#strictness

Unfortunately this ship sailed at Filecoin launch and changing this now requires a bit more work. I'd love to see this done, however.