Refactor communication and storage of optimization results

[verveerpj]

Issue Optimization results are currently stored in an SQLite database, which is used by Everest via a snapshot object to report and store results. This approach is not directly supported anymore by the ropt which is used by Everest to run the optimization. Everest uses the seba-sqlite package which provides the original code from Seba to support the SQLite database.

This code should be replaced in Everest for the following reasons:

• Reliability issues with the SQLite database, in particular on NFS files systems.
• Performance is poor.
• The code has not kept up with new features that have added in recent years, impeding proper monitoring and storage of results. For instance, when auto-normalization is used, the console output does not handle scaled results properly due to missing information.
• The seba-sqlite code is deprecated, TNO will not continue to support it.

Instead of using the database, Everest should receive optimization results directly from ropt via the provided callback mechanism, and take appropriate actions to report and store results.

Definition of done When the SQLite code has been removed from Everest and all current reporting and storage functionality is available.

Blocked by https://github.com/equinor/everest/issues/118