[ML] Better handling for permission errors during analytics job run time

[pheyos]

When permission issues occur during the data frame analytics execution, the UI doesn't inform the user properly.
A lot of the needed permissions are already checked before creating/starting the job, but the permission model gets more complex over time, so we should also include graceful error handling during run time.

Example:

• Try to give a user all needed permissions to create and run data frame analytics jobs based on the errors the user sees during job creation (assuming that when no error is displayed any more, all needed permissions are granted).
• You end up with permissions close to the documented ones (https://www.elastic.co/guide/en/elasticsearch/reference/7.6/start-dfanalytics.html) but in this case the permission indices:admin/refresh (contained in manage index permission) is missing.
• The job can be created and started without issues and it finished phase 1 (reindex) fine.
• Then the job doesn't continue to do anything and no error message is displayed.
• The error is only logged to the ES log:

org.elasticsearch.ElasticsearchSecurityException: action [indices:admin/refresh] is unauthorized for user [analytics_admin]

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[peteharverson]

Fixed by #60249. The failure reason for the job is displayed in the EuiBadge tooltip in the data frame analytics job list (previously tooltip was not displaying the failure reason), and an EuiBadge has been added for the display of the job state to highlight errors in the expanded row for the job.