Towards immutable BindingsMap in Java

[JaroslavTulach]

Pull Request Description

Initial rewrite of BindingsMap to:

• minimize the moving parts by having immutable State that can be replaced at once in the best tradition of TransactionalDataStructures
• move the implementation towards Java by adding a BindingsMapBase superclass

The goal is:

• keep old BindingsMap functionality unchanged
• move all the immutable getters into the base class: a3a3a98
• turn the BindingsMapBase to fully transactional structure

Later also:

• make sure updateState calls are really "pure functions"

Checklist

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

• All code follows the
  Scala,
  Java,
• No tests are broken
• Engine benchmarks run is OK

[github-actions]

✨ GUI Checks Results

Summary

• 🧹 Prettier: ✅ Passed
• 🧰 GUI Checks: ❌ Failed
• 📚 Storybook: ❌ Failed

⚠️ Action Required: Please review the failed checks and fix them before merging.

See individual check results for more details.

[JaroslavTulach]

• the 37293c7 version
• seems to be relatively green in engine jobs
• as well as IDE jobs
• let's try another step
• let's "move all the immutable getters into the base class"

[JaroslavTulach]

• the getState() method and the updateState(...) methods turn
• the BindingsMapBase into fully transactional data structure
• if the updator function passed into updateState is pure function from State to State then:
  • no state update can be lost
  • the final state includes all performed updates
• no matter how many threads is trying to update the binding map

[Akirathan]

LGTM