enhance contract api to use a build => execute architecture

[lllwvlvwlll]

in many cases, our tools can see substantial performance improvements (order of magnitude) by posting multiple transactions at the same time. Currently, we only support single transactions running at a time, which causes massive performance overhead (each transaction needs to be published before issuing another).

This enhancement implements a raw transaction builder which is wrapped by the api. This allows us to build multiple transactions and send them together in a single request in our applications, while allowing the end user to continue using the higher level methods.

[rockacola]

Just to clarify,

• We want to implement a helper method that allow us to submit multiple claims in 1 method, correct?
• @lllwvlvwlll you want to focus on performance, correct? Ie/ by simply serialize the claim invocations are not good enough, we'll need to have a method to potentially parallelize claim submissions in order to speed up overall completion, correct?

[rockacola]

@lllwvlvwlll is this ticket addressed with creation of NeoVivid.getDecryptedClaimByClaimID?

[lllwvlvwlll]

No, this is specifically in reference to methods which publish data to the chain.