Add support for cut cheat code

[anvacaru]

Fixes: #23

Added a new cut cheat code that takes a program counter and will create a new KCFG node whenever that program counter is executed.

• When the cut is executed in a proof/test, the program counter argument is added to a set in the cell.
• The #pc [ OP ] rule is overwritten to identify when a program count in the cell is executed.
• Added an empty foundry.cut rule and marked it as a cut-point rule to create the new node in the kcfg.

TODO:

• add test
• update expected output
• extract cut cheat code in the cheat code library after this PR is merged

[lucasmt]

I tried the cut cheatcode at the example from PR #162, but it didn't seem to be working. I used kontrol section-edge to look closer at what's going on, and I found that it was just skipping from #next to #execute without going through #pc (which is what should trigger the #cut instruction):

┃  │  (1 step)
┃  ├─ 122
┃  │   k: #next [ PUSH ( 2 ) ] ~> #execute ~> CONTINUATION:K
┃  │   pc: 4690
┃  │   callDepth: 0
┃  │   statusCode: STATUSCODE:StatusCode
┃  │
┃  │  (1 step)
┃  ├─ 123
┃  │   k: #execute ~> CONTINUATION:K
┃  │   pc: 4693
┃  │   callDepth: 0
┃  │   statusCode: STATUSCODE:StatusCode

I think this is because of the optimizations in the optimizations.md file. Not sure what's the best way to get around this.

[lucasmt]

Additionally, I think the cheatcode also won't work if the PC is arrived at from a JUMP instruction. Although this might not be as big of a problem since one can just use the PC immediately following the JUMPDEST.

[anvacaru]

Closing this for now.