Ensure naming of Columns resulting from Column operations is consistent.

[wdanilo]

This task is automatically imported from the old Task Issue Board and it was originally created by Radosław Waśko.
Original issue is here.

---

Currently in-memory operations call all resulting columns Result and DB operations inherit the name of the original column. That is inconsistent.

In other places we were discussing adding a new_name parameter to the operations so that the user can pick a new name.

The goal of this ticket is to fix both of these:

• extend all column operations with a new_name parameter allowing to set the name of the operation's result.
• come up with some sane defaults for the new_name and make sure that they are consistent between backends.

The algorithm for the default new_name could be:

• <op name> of <original column name> for unary operations,
• for binary operations it gets complicated as the operand may be another column or just an Enso object, we could do: <op name> of <original column name> and <other column name or objects's type> so stuff like Sum of A and B or Sum of A and a Text.