Specifying evaluation module of visualization preprocessor.

[farmaazon]

Summary

The @kustosz 's comment regarding current visualization API:

The current documentation (https://github.com/enso-org/ide/blob/main/src/rust/ide/view/graph-editor/src/component/visualization/foreign/java_script/definition.rs#L55) describes setPreprocessor as taking a code string.
However, I find it important to also handle the second parameter exposed by the backend – the evaluation module:
https://dev.enso.org/docs/enso/language-server/protocol-language-server.html#visualisationconfiguration

This is important to ensure visualizations can be created independent of the data definitions.
If you don't want to always pass this argument, a sensible default would be the module Main of the project defining the visualizations (not the current project! the project that defines the visualisation). However, an option to override should be available.

Value

See above

Specification

So, the setPreprocessor function could take an additional optional argument with the module name, and set it in the Engine. The default module should be as described above + the builtin visualizations should have Base.Main (perhaps).

Acceptance Criteria & Test Cases

Run IDE, show some visualization and see the messages sent to Engine in Network tab.

[MichaelMauderer]

When resolving this, please also revert the workaround in geoMap.js#L14`.