Expression update contains full multi-value info

[4e6]

Pull Request Description

close #12153

Important Notes

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated, if necessary.
• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Scala,
  Java,
  TypeScript,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• Unit tests have been written where possible.
• If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
  or the Snowflake database integration, a run of the Extra Tests has been scheduled.
  • If applicable, it is suggested to paste a link to a successful run of the Extra Tests.

[JaroslavTulach]

Make this safer:

• assert the first publicType.length part is the same in both arrays
• change the format of the message to avoid this array equlibristic

[JaroslavTulach]

This is (again) an incompatible change in the protocol. Shouldn't we rather start to be compatible in the absence of #7717? What about:

• keeping expressionTypes unchanged
• adding optional dispatchTypes with publicTypes = typeOfNode.findAllTypesOrNull(value, false);
• note that when dispatchTypes are missing, then the first type of expressionTypes is dispatchable

[JaroslavTulach]

I am not sure I like the terminology:

• maybe we use visible type somewhere
• but we certainly never used conversion type!

The documentation is using following terms:

• "has been cast to (the visible part)"
• "hidden types .... can be cast to."

I understand that the current terminology isn't perfect. We can change it, but consistently. We shouldn't be inventing conversionType term in the protocol only. If we want new term, we should update (at least) docs as well.