Simulate: Hash of Program Bytecodes in Simulation

[ahangsu]

Summary

This PR implements #5567, which returns hash digests of program bytecode being executed during simulation.

Test Plan

Extending pre-existing simulation tests and rest client tests on execution trace, and activate initial-state-config which returns program bytes.

[CLAassistant]

All committers have signed the CLA.

[codecov]

Codecov Report

Merging #5658 (9a6c040) into master (3425e85) will increase coverage by 0.03%.
Report is 9 commits behind head on master.
The diff coverage is 55.55%.

@@            Coverage Diff             @@
##           master    #5658      +/-   ##
==========================================
+ Coverage   55.15%   55.19%   +0.03%     
==========================================
  Files         465      465              
  Lines       65024    65042      +18     
==========================================
+ Hits        35862    35897      +35     
+ Misses      26769    26760       -9     
+ Partials     2393     2385       -8     

Files Changed	Coverage Δ
daemon/algod/api/server/v2/utils.go	7.43% <0.00%> (-0.19%)	⬇️
ledger/simulation/trace.go	83.05% <ø> (ø)
ledger/simulation/tracer.go	95.55% <100.00%> (+0.20%)	⬆️

... and 13 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[ahangsu]

By live discussion, while unknown if it is interesting to return program byte code, I decided to divert this PR into exposing executed program bytecode's hash in simulation exec trace, and this should help debugger to pair sourcemap + teal source code with execution trace.

[jannotti]

This looks like a good way to let debuggers know they've got the right program ready to step through.
Since this is a small value, and quick to compute, I don't think we should add options to include or not include this. The number of config flags is getting a little out of hand. Let's just always include it. I think that with JSON responses it's legitimate to add something new and still consider in "unbreaking", right?

[ahangsu]

yea, even better, we can just return the hash as some always return part. JSON wont just break easily if we add something to it, sdks just ignore such field (for now)

[ahangsu]

oh snap, I should include hash for every test now.

[bbroder-algo]

A hash-slinging slasher.

[jasonpaulos]

Looks good only minor nits