Allow fall-through in switch

[jannotti]

Moved opcode number to be by other "strange jumps"

Added simple tests for normal cases, and for fallthrough

[algochoi]

Do we want to bump up the doc version here or later down the road? It looks like the docs weren't regenerated:

https://github.com/jannotti/go-algorand/blob/c066ff29baec7d5347891e7264388111d15fbd80/cmd/opdoc/opdoc.go#L31

var docVersion = 7 // -> change to 8

[michaeldiamant]

Do we want to bump up the doc version here or later down the road?

@algochoi It's a good callout. Since AVM 7 is fully out the door, I think we can bump it. I leave it up to @jannotti - I'd probably do so in an isolated PR because multiple opcodes' docs will be enabled.

[jannotti]

I think all we need to do first is make sure that devrel (or whoever does it) has taken the v7 docs and put them in place for public consumption.

[michaeldiamant]

@jannotti https://github.com/algorand/docs/blob/staging/docs/get-details/dapps/avm/teal/specification.md looks updated to me. As a live proof point, opcodes look updated: https://developer.algorand.org/docs/get-details/dapps/avm/teal/opcodes/.

The repo recently introduced Github Actions to automatically generate PRs when there's upstream (go-algorand, indexer) releases: https://github.com/algorand/docs/blob/staging/.github/workflows/release-checker.yml.

Due to the auto PR generation, I think we want to hold on merging updated docs to master until ready to release AVM 8. So, we can either have a long-lived branch/PR previewing doc changes or hold until release gets set in motion. I don't feel strongly - either option works for me.

[jannotti]

I bumped the docVersion, moved pairing ops to 9, and put in the v9 nonsense test.