[Stack Monitoring] Fix enable_monitoring functional test

[klacabane]

Only one test there. Failing for a missing test-subj attribute noDataContainer.

cmd:
node scripts/functional_test_runner --config x-pack/test/functional/config.js --grep "Monitoring app Monitoring" --quiet

...
       └-> "after all" hook for "Monitoring enabled"
       └-> "after all" hook for "Monitoring enabled"
     └-> "after all" hook in "Monitoring app"
 
 0 passing (2.0m)
 1 failing
 
 1)    Monitoring app
        Monitoring is turned off
          "before all" hook for "Monitoring enabled":
 
       Error: retry.try timeout: TimeoutError: Waiting for element to be located By(css selector, [data-test-subj="noDataContainer"])
  Wait timed out after 10053ms

[elasticmachine]

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

[klacabane]

Added the noDataContainer subj and now got a failure trying to target the Refresh button which has a querySubmitButton test-subj. Looks like we're using a dependency (EUI) component for that, I'd expect both versions to use it but somehow the test-subj is not appearing in the react version, so I guess they are two different ones ? I'll look into that.

Now why are we clicking this refresh button on a NoData page ? Looking at git history it appears that it was initially to Handle cloud test failures, but I can't find an explanation as to why it fixed the issue. Moving up the history we see that these tests were disabled for cloud sometime later. So for now It seems safe to remove this step to cleanup unnecessary code, remove a dependency on 3p component and also to unblock me :).

[klacabane]

Tests are passing on angular version after removing the "click refresh button" step but they're still failing for react on the following step when trying to locate the clusterOverviewContainer > clusterName element

[estermv]

Tests are passing on angular version after removing the "click refresh button" step but they're still failing for react on the following step when trying to locate the clusterOverviewContainer > clusterName element

@klacabane I fixed this error on my PR: #114982

[klacabane]

Confirming test pass smoothly with @estermv change. I'll submit PR

[matschaffer]

PR is merged and we passed CI, so calling this done. @klacabane if there's more work to do please add it to #115026