Convert Visualize Editor to New Platform

[timroes]

Conversion of the "visualize editor" (aka default editor) to new platform. The main folder folder of the editor is src/legacy/ui/public/vis/editors/default (though controls are fragmented in many other places too). The visualize editor consists of the following features/components:

• Visualize Editor Frame (Apply/Revert, Sidebar, Tabs)
• Data panel (Aggregation selection)
• Individual options panel for all visualizations

The following tasks need to be done:

• Move visualize editor to new platform
• Move UI to React (EUIfication)
  • Visualize Editor Frame (EUIficate visualize editor frame #38272)
  • Data panel (EUIficate vis editor data panel #30922) - DONE
  • Individual Options panels (EUIficate visualization option panels #38273) - IN PROGRESS
• Completely remove Angular (Even after EUIfication a lot of clue code is still in Angular that needs to be removed)

[elasticmachine]

Pinging @elastic/kibana-app

[thompsongl]

@timroes Is there a timeline to the "Completely remove Angular" part?

EUI is looking to implement some changes to a form control (EuiSwitch), but the changes don't jibe with the Angular dirty checking mechanism used in the Vis Editor options panel (see elastic/eui#2255).

Wondering if waiting for the complete removal of Angular is the right approach, or if we should look into a shim to set $touched/$dirty.

[timroes]

I think you most likely don't want to wait for this. The idea is to have this removed in the next two month, but given that there is a lot of outstanding new platform migration (and we can actually run Angular in new platform), it might be that the final angular removal in the editor will fall short due to more important new platform work for now. So those 2 month are more a happy wish than an educated estimation :-)