Implement Enso-specific asserts

[Akirathan]

Implement something like this:

Runtime.assert : (Any -> Boolean) -> Text -> Nothing
Runtime.assert ~action msg="" =
  if assertions_enabled_builtin.not then Nothing else
    if action.not then Panic.throw ("Assertion Error: " + msg) else
      Nothing

(where assertions_enable_builtin is a builtin method that just check an Assumption in EnsoContext)

Assertions will be enabled with ENSO_EA=true environment variable.

Implement it via truffle Assumption in EnsoContext, so that Runtime.assert is a no-op if assertions are disabled.

JVM assertions and Enso assertions can be enabled separately.

[radeusgd]

Subjective, but I would suggest to call the env var ENSO_ENABLE_ASSERTIONS. It's not much more typing but it is much clearer what this variable is doing vs EA which is rather cryptic. And it would be more aligned with our style guide.

[radeusgd]

Also, I'm really excited to see this feature implemented, I've been dreaming about it for a while, just never had enough spare cycles to get it done!

I think asserts are a really great help for ensuring correctness and they act as additional documentation of programmers intent. So I appreciate this.

[enso-bot]

Pavel Marek reports a new STANDUP for today (2023-09-27):

Progress: - Almost finished, just have to write few more tests, and make sure that assertions are enabled on the CI It should be finished by 2023-09-29.

[enso-bot]

Pavel Marek reports a new STANDUP for today (2023-09-28):

Progress: - Trying to use jUnit 5 Jupiter, but failed to integrate that - #7915

• At least using some hamcrest matchers in the new tests.
• Writing rest of the tests
• Finished the implementation, should merge tomorrow after final review. It should be finished by 2023-09-29.