Separate Interrupts and Callbacks. Make mouse CALL instruction explicit in memory

[kevinferrare]

Mistakenly merged #359 so here it is again.

Description of Changes

Make a clear distinction between Callbacks and Interrupt handlers:

• Callbacks are C# code behind a custom ASM instruction
• Interrupt handlers are C# classes that install themselves in memory as ASM, and that can rely on Callbacks to ensure their C# code is called from emulated ASM

Mouse interrupt handler now works like this:

// Responsible for Regs storage and setup. Does not change stack and CS:IP anymore.
CALLBACK 0x74
// User function address is written by CALLBACK 0x74
CALLF <User Function Address>
// Responsible for regs cleanup as before
CALLBACK 0x90
IRET
// Default user function, does nothing
RETF 

Had to change dumped json library because Newtonsoft one did not like SegmentedAddress having 2 constructors and was ignoring [JsonConstructor]

Example of the mouse handler int in ghidra (callback replaced by int because ghidra wouldnt understand):