adds support for mode events

[thestr4ng3r]

Depends on BinaryAnalysisPlatform/bap-frames#17
which depends on BinaryAnalysisPlatform/bap#1433
and for tracing: BinaryAnalysisPlatform/qemu#17

Mode events from bap-frames traces, indicating for example whether an
instruction is executed in thumb mode or not, are now taken into account
for disassembly and lifting. This enables chcecking traces from qemu
running arm code with interworking.

As a consequence of possibly requiring different disassemblers per
frame and respecting the mode, the code has been refactored to locally
use the KB to derive target and encoding for Dis.lookup instead of
running everything in Dis.with_disasm.

Here is an example trace:
emulateme.arm32.frames.gz
Results:

|-------------------------------|
|             | rel    | abs    |
|-------------+--------+--------|
| overloaded  | 0.00%  | 0      |
| undisasmed  | 0.00%  | 0      |
| misexecuted | 3.76%  | 4685   |
| mislifted   | 0.00%  | 0      |
| damaged     | 0.00%  | 0      |
| successed   | 96.24% | 120053 |
|-------------------------------|

notice how nothing was undisasmed

[thestr4ng3r]

There are still a few things here that are just dirty hacks.
Before, the disas was created using Dis.with_disasm ~backend:"llvm" (Arch.to_string arch), but I wasn't able to figure out (yet) how to shoehorn the encoding in there correctly. From what I can tell, this will internally almost directly pass the given triple to llvm.
So instead, I now use Dis.lookup and try to somehow derive the core theory target and language from my given arch and encoding string, but this is still hardcoded/partially broken and I don't really know how to do it right yet.