Algod: Simulation PC exposure for App approval/clear-state transaction

[ahangsu]

Summary

This PR implements #5012, which exposes PC during simulation for each txn-group.

Test Plan

1. simulation_eval_test.go:
   a. recursive inner calls that creates app, calls app and deletes itself.
   b. app-call transaction approved through a logic sig.
   c. a vanilla app-call transaction together with extra budget supply.
2. restClient.go:
   a. an e2e test that tests recursive inner calls that creates app, calls app and deletes itself. See if trace work as expected

[codecov]

Codecov Report

Merging #5360 (d392f99) into master (a10efe5) will increase coverage by 0.01%.
The diff coverage is 58.59%.

@@            Coverage Diff             @@
##           master    #5360      +/-   ##
==========================================
+ Coverage   55.31%   55.32%   +0.01%     
==========================================
  Files         452      452              
  Lines       63844    63936      +92     
==========================================
+ Hits        35313    35372      +59     
- Misses      26101    26132      +31     
- Partials     2430     2432       +2     

Impacted Files	Coverage Δ
daemon/algod/api/server/v2/handlers.go	0.82% <ø> (ø)
daemon/algod/api/server/v2/utils.go	10.42% <0.00%> (-1.42%)	⬇️
data/transactions/logic/eval.go	91.24% <0.00%> (-0.03%)	⬇️
node/node.go	4.04% <0.00%> (ø)
cmd/goal/clerk.go	8.88% <16.66%> (+0.05%)	⬆️
ledger/simulation/trace.go	84.44% <46.15%> (-5.80%)	⬇️
ledger/simulation/simulator.go	75.55% <83.33%> (-1.72%)	⬇️
ledger/simulation/tracer.go	92.25% <96.61%> (-1.37%)	⬇️
daemon/algod/api/server/v2/test/helpers.go	74.74% <100.00%> (ø)

... and 16 files with indirect coverage changes

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

[jannotti]

This is looking quite close. I mostly have some concerns about naming, and whether we can simplify the interface between "internal" structs and models. I may well be wrong about how pointers are handled in serialization. I think @jasonpaulos is a bit of an expert here.

[jasonpaulos]

Pending tests, looks good