Improve address computation accuracy
Clarification and motivation
This issue stems from TM-62. In !424 (merged) we have increased address computation accuracy by taking counters into account. However, it still uses JSON encoding instead of standard Michelson encoding. Some preliminary work for proper encoding has been done in !414 (closed). We should finish that work.
Note that it's likely better to do https://issues.serokell.io/issue/TM-273 first.
Acceptance criteria
Smart contract address computation serializes contract using the same way approach that the reference client uses instead of currently used JSON. Byte-to-byte compatibility is not a strict requirement, but it'd be nice to achieve that.
Edited by Ivan Gromakovskii