Add range info to Out_Of_Range error

[GregoryTravis]

Followup from #9462.

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,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• All code has been tested:
  • Unit tests have been written where possible.
  • If GUI codebase was changed, the GUI was tested when built using ./run ide build.

[radeusgd]

The message is ignored in to_display_text - but that is the user-facing text where it definitely should be included too.

Also please add a test of to_display_text - as I mentioned in some review recently - we used to have regressions in these and if they do not have unit tests, we learn about these only when they occur in the IDE - which may be found rarely if the warning is not one seen every day.

[GregoryTravis]

The message is ignored in to_display_text - but that is the user-facing text where it definitely should be included too.

Also please add a test of to_display_text - as I mentioned in some review recently - we used to have regressions in these and if they do not have unit tests, we learn about these only when they occur in the IDE - which may be found rarely if the warning is not one seen every day.

Yes, I forgot to change that one -- done.

[jdunkerley]

looks good - might be worth having the limit in the message for clarity.

[GregoryTravis]

looks good - might be worth having the limit in the message for clarity.

Added.