Add replace_text method to In-Memory Table

[Frizi]

Pull Request Description

Implements https://www.pivotaltracker.com/n/projects/2539304/stories/183415329

Important Notes

Checklist

• The documentation has been updated if necessary.
• All code conforms to the
  Scala,
  Java,
  and
  Rust
  style guides.
• All code has been tested:
  • Unit tests have been written where possible.
  • If GUI codebase was changed: Enso GUI was tested when built using BOTH
    ./run ide build and ./run ide watch.

[CLAassistant]

All committers have signed the CLA.

[radeusgd]

Looks good to me, I really like the tests 😁

Ideally, I think we should have the replace operation also implemented as a vectorized operation on StringStorage (see for example how Column.like is implemented) - it would likely be quite a bit faster because Column.map is slow due to constant switches between Java and Enso. But I'm not sure if that is in the scope of this task - so I think this is free to go and we can think about the optimizations in the future too.

[radeusgd]

This check was originally in wrong order - if result.stack was empty the latter would be false, but before it's checked we'd call result.stack.head which would throw an exception (due to an empty stack).

For some reason the changes in this PR have started triggering this. It is a bit curious why, but I think we should just have it changed to correctly finish the loop if the stack is empty.