Fix TypingResult.valueOpt for the purpose of SpEL validator

[wrzontek]

Describe your changes

Checklist before merge

• Related issue ID is placed at the beginning of PR title in [brackets] (can be GH issue or Nu Jira issue)
• Code is cleaned from temporary changes and commented out lines
• Parts of the code that are not easy to understand are documented in the code
• Changes are covered by automated tests
• Showcase in dev-application.conf added to demonstrate the feature
• Documentation added or updated
• Added entry in Changelog.md describing the change from the perspective of a public distribution user
• Added MigrationGuide.md entry in the appropriate subcategory if introducing a breaking change
• Verify that PR will be squashed during merge

[wrzontek]

It just came to me that this could be the case for other classes being incompatible between java and scala for the purpose of SpEL validation, I'll check them tomorrow.

[wrzontek]

this needs to be addressed more throughly now that i've slept on it

[wrzontek]

CI passes except for known flaky k8 test failures

[wrzontek]

Limitation: as with selection/projection, some #COLLECTION helper methods also mostly lose value (not a regression, value is lost in cases where before it wasn't even kept)

Keeping value could probably be implemented for all of them, with varying degrees of difficulty/jank (easy example: concat, merge, complicated example: product, shuffle etc.)

[wrzontek]

merging after re-approve from @mslabek