Enable caching in visualization functions

[4e6]

Pull Request Description

PR allows to attach metod pointers as a visualization expressions. This way it allows to attach a runtime instrument that enables caching of intermediate expressions.

Important Notes

ℹ️ API is backward compatible.

To attach the visualization with caching support, the same executionContext/attachVisualisation method is used, but VisualisationConfig message should contain the message pointer.
While VisualisationConfiguration message has changed, the language server accepts both new and old formats to keep visualisations working in IDE.

Old format

{
    "executionContextId": "UUID",
    "visualisationModule": "local.Unnamed.Main",
    "expression": "x -> x.to_text"
}

New format

{
    "executionContextId": "UUID",
    "expression": {
        "module": "local.Unnamed.Main",
        "definedOnType": "local.Unnamed.Main",
        "name": "encode"
    }
}

Checklist

Please include the following checklist in your PR:

• The documentation has been updated if necessary.
• All code conforms to the
  Scala,
  Java,
  and
  Rust
  style guides.
• All code has been tested:
  • Unit tests have been written where possible.
  • If GUI codebase was changed: Enso GUI was tested when built using BOTH
    ./run ide dist and ./run ide watch.

[JaroslavTulach]

I am surprised there is a change needed in the engine. Especially the change in callArguments in FunctionCallInstrumentationNode is surprising.

[hubertp]

Suggested change

	|""".stripMargin.linesIterator.mkString("\n")
	|""".stripMargin

isn't this bit spurious? This is equivalent, right?