Viper IDE refactoring: Debugger

[WissenIstNacht]

This issue pertains to the ongoing refactoring process #113.

Viper IDE provides advanced debugging features, using the debugger extension. Currently, the debugger extension is mainly managed by the Viper IDE language server (see DebugServer.ts). With the current refactoring of Viper IDE, the responsible code will be removed. It should therefore be reimplemented in the refactored version of this codebase.

It is unclear what the best course of action for this refactoring step is. Currently, Viper IDE's language server is responsible for orchestrating communication between the debugging extension, the verification engine, and the Viper IDE client. All of these modules perform some tasks related to debugging. Ideally, the code in the language server that orchestrates communication between the various parts and that manages the debugging extension would be moved to ViperServer. However, it is unclear how well ViperServer would be able to manage a VS Code extension. An alternative would be to move the management and coordination to the client while having all the computation related to debugging done in ViperServer. The client would then act as a relay between the debugging extension and ViperServer.