Context

Currently native composite values (e.g. AuthAccount, AuthAccount.Contracts, PublicAccount, etc.) are defined through separate Go types implementing the Value interface (e.g. AuthAccountValue).

Refactor those existing value type to use CompositeValue instead.

Pros:

• No need to declare new Value type, reduce boilerplate
• No special conversion functions in internal encoding/decoding and import/export

Definition of Done

Non-exhaustive list:

• AuthAccountValue
• PublicAccountValue
• AuthAccountContractsValue

Not good candidates:

• PathValue
• LinkValue
• StringValue