Indirect Jumps: Trace -> Static (x86, x86-64 support for now)

Here's pull request part 2. We mark indirect jumps in disasm when we see them. I can test this a bit more before I merge, but I wanted to highlight a question I had when I was implementing this. Notice in qira_analysis that I wasn't sure if we were able to call a function pointer stored in memory. I can get the memory there, but it didn't seem to be right (not an address, usually something much smaller, and I'm pretty sure I'm getting the correct amount of bytes depending on the arch). It seems like indirect jumps/calls with pointers in memory happen when we do library calls which don't get traced into, so that was one possibility that came to mind.

Anyways, maybe I'm just confused about what's going on here but in that case, the edges definitely weren't right, so I didn't add them. Once I get that cleared up this should be merge ready, as everything else appeared correct.