Support Table mixin columns

This is essentially the same as #1833, #1835, #1839 but will be done in the framework of #2790 as a follow-on once that is merged.

The starting point here will be fed00dc5f6d6d9529ed8f073c95346eb176fdfa6, which *removed* the proof-of-concept changes showing that mixin columns would be straightforward in the new column-based Table structure.   In this issue (and eventual PR) we can define the right way to support mixin columns like Quantity, Time, and SkyCoord.  The original proof-of-concept used a some simple class / instance variables, but @mhvk has proposed using an abstract base class.

Closes #1833
Closes #1835
Closes #1839
As noted above, I think it might be somewhat cleaner if `Table` everywhere assumes it is a regular `Table` and here you overwrite only those methods that make a difference. It seems that this would only be `_is_mixin_column` and `_init_from_cols`! (Quite surprisingly few, which suggests the code is very nicely abstracted!)