[Table Visualization] manual tests on new Table Vis features and track bug fix

[ananzh]

Manual Tests on Features

We are shifting table visualization from angular to react using DataGird. From our current understanding, there is no breaking changes. We expect no customer impact when upgrade to newer OSD version. Therefore, we are targeting to release table vis in a minor version.

To fulfill this, there are two main questions on feature tests of Table Vis.

• Backward compatibility: Are current customers able to use table vis if upgrade?
  No breaking change means any saved table visualizations from released 1.* to 2.3 OSD should be able to 1) shown correctly in saved object 2) display and function correctly

• Missing features: Are all the current features from table vis be transferred to new table vis?
  No breaking change means no missing features.

This purpose of this issue to document all the feature-wise tests and backward compatibility results. If there is any breaking changes we observe and could not be resolved, we need to release table vis in the next major version.

[ananzh]

[Split Feature Tests][BUG] Split tables are not sharing column width states
Table Visualization can be split based on rows and columns. Currently, if we split tables and then if resize the column, only the selected split table is updated. However, this seems not right. When we resize or sort the column, we are changing the state vis.columnsWidth and vis.sortColumn which should be shared by all splitted tables.

Fix PR:
#2582

[ananzh]

[Split Feature Tests][IMPROVE] remove repeated column in split tables by col
Currently, when we split table by columns, the split column is shown both in the table title and as a separate column. In below example, a separate city col is not needed because the whole table is for that specific city. We could produce a cleaner table vis by removing the repeated column.

FIX PR
#2583