Issue to cover the work to move the ML index data visualizer into a separate plugin.

Background

The index data visualizer allows users to view their indices and quickly get an understanding of the fields in their data using top values, maps and other quick views to show metrics and values in the data. It provides a contextual view into indices to show which fields are getting used, how many documents contain those fields, and the number of unique values and distribution in the field.

Apart from being a powerful part of the ML workflow, this tool has wider applications across Kibana, such as in Discover, where it could be added as an additional view into an index - see #97176. In order to facilitate this, the code should be moved out of ML into a separate plugin, in a similar approach as was recently completed for the file data visualizer - see #96408.

Progress

• Move file upload endpoints into its own plugin
• Move File Data Visualizer into its own plugin [ML] Moving file data vizualizer to its own plugin #96408
  • Move files that related to the file/import page into new file_data_visualizer plugin
  • Add index_exists and time_field_range endpoints to the fileUpload plugin to assist with importing data
  • Move the analyze_file endpoint from fileUpload to fileDataVisualizer
• Move Index Data Visualizer into file_data_visualizer plugin
  • Migrate index based files to new plugin
  • Move get_overall_stats and get_field_stats routes and services to internal/data_visualizer
  • Re-organize structure of folders into common, file_data_visualizer, and index_data_visualizer
  • Update types
    • Replace deprecated IIndexPattern with IndexPattern and replace deprecated IFieldType with IndexPatternField
    • Replace RuntimeMappings with estypes.RuntimeFields
  • Add back preview for Boolean type