Allow a Table to be used to rename_columns.

[jdunkerley]

Pull Request Description

Following an example from Steve, adjusted rename_column to allow a Table to define the mapping.

• A single Text column table gives a list of new names.
• A two Text column table gives a map from old name to new name.
• If a DB_Table is passed errors and tells the user to materialize the table.

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.

[radeusgd]

Looks good, but I think we should test the error scenarios as well (using DB table with DB table and with in-memory table).

Because Enso language is so dynamic, I just can't trust an error scenario that is untested - we've historically had far too many cases of untested error scenarios that actually crashed because of a typo. Well, at least I wouldn't trust myself about it if I had written this without tests.

[radeusgd]

Sounds much better :)