Fix: Machine is a God class

[maximilien-noal]

Description of Changes

Removes all the references to the Machine in the Emulator core, reverse engineeering classes, GDB namespace, exceptions, and the UI.
Moves the DMA loop and DMA thread to the DMA Controller class.
Moves the emulation loop and the emulation thread to a new EmulationLoop class.

All in all, removes all TrainWrecks (aka Law of Demeter violations) related to the Machine.

The Machine is now close to being removed entirely. It's only a dumb service container.

It is only created and used by the Program Executor and unit tests.

But removing it entirely would need the usage of Pure.DI (already used on the UI side), which requires interfaces.

There are also no cyclic dependencies between:

• The CPU and the DualPic. It is instantiated by the CPU.
• The CPU and the ExecutionFlowRecorder. It is instantiated by the CPU.
• The CPU and the IOPortDispatcher
• The CPU and the Callback Handler
• The CPU and the MachineBreakpoints

Rationale behind Changes

Makes the code more SOLID, more testable, and way easier to work with.
All classes or nearly all of them only access their toys and their friends, they do not overreach.
Fixes #338

Suggested Testing Steps

Already manually tested:

• emulation
• UI

To be tested against master very soon (by me) - but should still be working:

• Reverse engineering classes (ExecutionFlowRecorder, RecorderDataWriter, and friends)
• GDB

[JorisVanEijden]

What is the purpose of these public properties? They do not seem to be related to the concept of a programexecutor.
Is this the ProgramExecuter taking over some of the "servicecontainer" functionality of the Machine?

[maximilien-noal]

This is a temporary fix so I could remove all references that where left in the MainWindowViewModel to the Machine.

[JorisVanEijden]

Looks good to me. Nice cleanup.