[ML] Support date_nanos time field

[peteharverson]

Support for the date_nanos was added to Kibana in 7.3.0 (see #36111), however various parts of the ML UI do not currently work when the time field of the Elasticsearch index is mapped as type date_nanos.

This meta issue tracks the functionality that needs fixing to support date_nanos type date fields:

• Validation in the job wizards fails, preventing the job being created ([ML] Anomaly detector job validation fails if time field is of type date_nanos #52921)
• 'Use full time range' button fails in the job wizards; page goes blank with an invalid bounds error in the browser console (no longer found in 7.7)
• 'Use full time range' button fails in the Data Visualizer; page goes blank with a TypeError in the browser console (no longer found in 7.7)
• Datafeed preview fails in the advanced job wizard, with an error of the form [illegal_argument_exception] date[+49916826-11-21T00:53:20Z] is after 2262-04-11T23:47:16.854775807 and cannot be stored in nanosecond resolution" (no longer found in 7.7)
• Transforms using a group_by on a date_histogram of the date_nanos field fail with BulkIndexingException seen in job messages (no longer found in 7.7)
• The preview table in the Transforms wizard show a blank column for the aggregation - caused by composite agg fails to bucket date_nanos with date_histogram source elasticsearch#53168. Fixed in [ML] Transforms: Fix date nanos preview rendering. #61792

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[peteharverson]

Closing as all items now addressed for 7.7.0.