Fixing small bugs uncovered by type checker

[radeusgd]

Pull Request Description

Once our libraries and tests are compiled with basic inference of method types, some warnings were reported:

X:\NBO\enso\built-distribution\enso-engine-0.0.0-dev-windows-amd64\enso-0.0.0-dev\lib\Standard\Database\0.0.0-dev\src\DB_Column.enso:1003:19: warning: Calling member method `div` on type Number will result in a No_Such_Method error in runtime.
 1003 |         halfway = scale.div 2
      |                   ^~~~~~~~~~~
X:\NBO\enso\built-distribution\enso-engine-0.0.0-dev-windows-amd64\enso-0.0.0-dev\lib\Standard\Image\0.0.0-dev\src\Matrix.enso:381:21: warning: Invoking a value that has a non-function type (type Image) will result in a Not_Invokable error in runtime.
  381 |     to_image self = Image (Image.from_vector self.normalize.to_vector self.rows self.channels)
      |                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
X:\NBO\enso\built-distribution\enso-engine-0.0.0-dev-windows-amd64\enso-0.0.0-dev\lib\Standard\Table\0.0.0-dev\src\Internal\Multi_Value_Key.enso:94:22: warning: Calling static method `new` on (type Illegal_State) will result in a No_Such_Method error in runtime.
   94 |         Error.throw (Illegal_State.new "Ordered_Multi_Value_Key is not intended for usage in unordered collections.")
      |                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This PR attempts to fix them.

There was also an expected error in the Examples:

X:\NBO\enso\built-distribution\enso-engine-0.0.0-dev-windows-amd64\enso-0.0.0-dev\lib\Standard\Examples\0.0.0-dev\src\Main.enso:139:36: warning: Calling static method `frobnicate` on (type No_Methods) will result in a No_Such_Method error in runtime.
  139 | no_such_method = Panic.recover Any No_Methods.frobnicate . catch
      |                                    ^~~~~~~~~~~~~~~~~~~~~

To avoid getting a warning, I wrapped this in (_ : Any) to make the warning go away. The behaviour of the function is unchanged.

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.

[radeusgd]

This assert is documenting that this method will not work if decimal_places > 0. That is because then scale would be a Float which has no div method, so it would fail at runtime with No_Such_Method error. That's what the checker uncovered.

All tests were passing so it's either never called with decimal_places > 0 or our tests don't cover all the cases.

@GregoryTravis do you know if this method is ever expected to be called with decimal_places > 0? It was unclear to me looking at DB_Column.round and should_use_builtin_round if that is the case or not.

[GregoryTravis]

Yes, I must be missing some test case. Added #11424.

[radeusgd]

Thank you