[CCR] Fixes CCR accessibility tests

[sabarasaba]

Closes #169512

Summary

This PR fixes the accesibility test for CCR thats currently broken due to using the wrong selector for enabling trust in remote clusters and attempts to fix the flaky test we had in follower indices for a while. I ran it 100 times locally and seems to be green every single time.

[sabarasaba]

@elasticmachine merge upstream

[sabarasaba]

@elasticmachine merge upstream

[sabarasaba]

@elasticmachine merge upstream

[sabarasaba]

@elasticmachine merge upstream

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 07de1a8

Failed CI Steps

• FTR Configs #46

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
remoteClusters	75.2KB	75.3KB	+64.0B

History

• 💔 Build #177821 failed 504a7c9
• 💔 Build #177497 failed d43d013
• 💔 Build #177496 failed d43d013
• 💔 Build #177363 failed cd7b051
• 💔 Build #177304 failed 65cf2b2

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @sabarasaba

[elasticmachine]

Pinging @elastic/platform-deployment-management (Team:Deployment Management)

[yuliacech]

Thanks a lot for looking into these tests, @sabarasaba!
The a11y fix LGTM: +1 The flaky jest tests are still a mystery, I think let's try enabling them and if we see any failures again, that might be the same issue as with Index Management and Watcher tests

[sabarasaba]

Thanks a lot for looking into these tests, @sabarasaba! The a11y fix LGTM: +1 The flaky jest tests are still a mystery, I think let's try enabling them and if we see any failures again, that might be the same issue as with Index Management and Watcher tests

Thanks for having a look! I've dig through quite a bit on them, and this particular test always seems to fail on CI with the timeout error, just doesnt happen locally (like ever). I havent been able to get a green CI with it so i think better to keep it disabled :(

[yuliacech]

Well at least it always fails on CI, that's something :D