[Stack Monitoring] New FTR for "view logs" link

[consulthys]

Summary

Closes #202675

A recent bug broke the Stack Monitoring UI only if/when logs were present. Functional test coverage was lacking to detect such a situation.

This PR adds some functional test coverage to make sure that the "View logs" link in Stack Monitoring works whenever logs are available, wherever logs can be visible, i.e. in the cluster overview page, the node details page and the index details page.

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: bc35db8

Failed CI Steps

• Jest Tests #10
• Jest Tests #10
• FTR Configs #2
• FTR Configs #2
• FTR Configs #101
• FTR Configs #101

Test Failures

• [job] [logs] Jest Tests #10 / Case Owner Selection renders all options
• [job] [logs] Jest Tests #10 / Connector renders loading state correctly
• [job] [logs] Jest Tests #10 / DeleteConfirmationModal calls onConfirm
• [job] [logs] FTR Configs #101 / Monitoring app Elasticsearch overview should show the link to view more cluster logs
• [job] [logs] FTR Configs #101 / Monitoring app Elasticsearch overview should show the link to view more cluster logs
• [job] [logs] FTR Configs #2 / Monitoring Elasticsearch node detail should summarize node with metrics
• [job] [logs] FTR Configs #2 / Monitoring Elasticsearch node detail should summarize node with metrics
• [job] [logs] Jest Tests #10 / useGetCaseUsers shows a toast error when the api return an error

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
monitoring	515.2KB	515.3KB	+69.0B

History

• 💔 Build #271670 failed 82a0a4d
• 💔 Build #271612 failed 1fc80a8
• 💔 Build #271509 failed ec9069c

cc @consulthys