Test ErgoScript -> ErgoTree compilation results are equivalent to sigmastate compiler

## Suggestion
Make a test suite with each test consisting of pairs of ErgoScript source code with expected compiled ErgoTree serialized and encoded as Base16. These pairs should be generated by sigmastate compiler initially and then they should be run as part of sigmastate tests to catch regressions.

Start by locating the existing sigmastate tests and the Rust entry points for ErgoScript-to-ErgoTree compilation. Use source-and-Base16 pairs generated by the sigmastate compiler as regression cases, and consider the work complete when the Rust tests verify equivalent serialized and encoded results.

Written by the indexing model from the issue text.