Cadence Compiler - phase 2

[j1010001]

Outcomes of this phase:

• Better understanding of what target(s) to consider
• Work towards specification of execution semantics, ensure correctness
• Address tech debt, make it easier to work on new functionality and reuse existing code for prototypes
• Proactive finding of security issues, improve security posture

### Main Tasks
- [ ] Add diagram of compilation “pipeline” to internal docs
- [ ] Compare RISC-V/Swift to Custom ISA/Go
- [ ] Add tracing to interpreter
- [ ] Investigate errors triggered by defensive checks (https://github.com/onflow/cadence/issues/3688)
- [ ] https://github.com/onflow/cadence/issues/3693

### Stretch-goals
- [ ] https://github.com/onflow/cadence/issues/3691

Notes Based on internal notes: https://www.notion.so/flowfoundation/Compilation-Discussion-1441aee1232480c897aed36c8f763e30