Pass intersection type thru the `-> Complex` check

[JaroslavTulach]

Pull Request Description

1st attempt to implement the -> Complex check. The idea is to split the list of types[] in EnsoMultiValue into two parts:

• first dispatchMethodTypes represent the types the value has been cast to
• the rest of the types represent the types the value can be cast to

By performing this separation I hope to address the #10882. After a type check only methods available on the dispatchMethodTypes can be invoked. However the value can still be cast to all the possible types.

Important Notes

@Akirathan, @radeusgd please check the idea, feel free to contribute new test cases. The goal of this PR is to get the dispatch/cast logic right. The next step would be to make it fast. So far some tests are failing, but the ideas in this PR shall already be eligible for a review.

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.

[Akirathan]

Idea for increasing test coverage of EnsoMultiValue: Manually create some Truffle nodes and explicitly call them. Inspiration from EqualsTest and HashCodeTest.

[JaroslavTulach]

Idea for increasing test coverage of EnsoMultiValue: Manually create some Truffle nodes and explicitly call them. Inspiration from EqualsTest and HashCodeTest.

• some EnsoMultiValue tests have just been created as part of #11618
• I have a much better feeling with such tests!