Add recipients arguments encoding

[samuelmanzanera]

Description

This PR aims to resolve an issue of inconsistency with JSON encoding, particularly with decimals.

Hence, it introduces a typed encoding approach of arguments and also use a different algorithm for the previous signature verification and the storage.

Previous signature tx's serialization happens with bit encoded on 1 byte (to simplify SDK and client integration), while for storage we can encode into 1 bit (Erlang allow us to optimize bitstring encoding easily)

Type of change

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[bchamagne]

I tested while developing the new version of the JS SDK.
I was able to trigger contracts with named action.

[samuelmanzanera]

👍