TEAL: Report columns in TEAL source maps

[jasonpaulos]

Summary

Prior to this, TEAL source maps would only map PCs to line numbers, always assuming the column was 0. Since multiple opcodes can now be placed on a single line, separated by ;, it makes sense to also report the source column as well.

Additionally, I also made the path to the source file relative to the source map file, which is what the specification requires (see Resolving Sources). Prior to this PR, we were just using whatever the user input as the source program path.

Test Plan

Existing unit tests updated and added an additional e2e test to expand coverage of more complicated cases.

[codecov]

Codecov Report

Merging #5776 (43f4090) into master (1a6d53e) will increase coverage by 3.94%.
The diff coverage is 65.27%.

@@            Coverage Diff             @@
##           master    #5776      +/-   ##
==========================================
+ Coverage   51.51%   55.45%   +3.94%     
==========================================
  Files         473      473              
  Lines       66688    66708      +20     
==========================================
+ Hits        34354    36993    +2639     
+ Misses      29742    27194    -2548     
+ Partials     2592     2521      -71     

Files	Coverage Δ
cmd/tealdbg/local.go	73.88% <100.00%> (ø)
data/transactions/logic/sourcemap.go	100.00% <100.00%> (+52.94%)	⬆️
daemon/algod/api/server/v2/handlers.go	0.79% <0.00%> (ø)
cmd/tealdbg/debugger.go	74.41% <81.81%> (+8.97%)	⬆️
data/transactions/logic/assembler.go	93.98% <75.00%> (+4.88%)	⬆️
cmd/goal/clerk.go	10.25% <37.50%> (+0.83%)	⬆️

... and 150 files with indirect coverage changes

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