Viper IDE refactoring: Settings

[WissenIstNacht]

This issue pertains to the ongoing refactoring process #113.

Viper IDE had a nubmer of settings describing various parameters (paths to tools used by the extension, which verification engine to use, timeouts, backend options, etc.). 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.

A description of the settings' structure can currently be found here:

viper-ide/client/src/ViperProtocol.ts

Line 329 in 4a49364

export interface ViperSettings {

However, with the refactoring of Viper IDE, this structure of settings is outdated. For example, there is no more need to set a verification engine. The refactored version of Viper IDE uses exactly one engine (namely, ViperServer running in language server mode). Another example related to this is that the use of stages is no longer necessary.

We therefore want to propose a restructuring of the settings. These restructured settings should then be synced with the refactored language server (i.e., ViperServer running in language server mode). This should allow the backend to be run with user-specified options (e.g. backend-specific cache, # of active jobs, timeouts, options for Silicon/Carbon, etc.), instead of the hard-coded parameters currently used.

Note that the counterpart of ViperProtocol.ts in ViperServer is called DataProtocol.scala. The structures of the settings in both files should be kept in sync. This will allow the communication of the setting between client and server using LSP.