[Security Solution] [Detections] Enabling ML jobs from Security App keeps trying when no ML Nodes Available

[MikePaquette]

Kibana version: 7.12.0 BC2

Elasticsearch version: 7.12.0 BC2

Server OS version: Elastic Cloud

Browser version: Chrome Version 88.0.4324.192 (Official Build) (x86_64)

Browser OS version: macOS Mojave 10.14.6

Original install method (e.g. download page, yum, from source, etc.): Elastic Cloud

Describe the bug:
When the cluster has no ML nodes, attempting to "Run job" from the ML Job settings drop down at the top of the detections page causes the job to try forever, with the spinner spinning.

Steps to reproduce:

1. Open Kibana
2. Open Detections page
3. Open ML Job Settings dropdown
4. Attempt to "Run job"

Expected Behavior
Some sort of failure message should be shown to the user, perhaps like this one, which is shown in the Machine Learning app overview page:

[elasticmachine]

Pinging @elastic/kibana-security (Team:Security)

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[spong]

Looks like this is a duplicate of #63155, and there's this related issue as well #54382.

[spong]

@MikePaquette -- reclassifying as impact:high as this has been present for nearly a year now, so we won't have a fix in for 7.12, but can prioritize for a future release.

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[MadameSheema]

Closing since is a duplicate of: #63155