Add CITs for index management to show hidden and rollup indices and update existing tabs test to reflect all tabs

[cuff-links]

Summary

This PR is to add the test coverage for showing system Indices and also for showing rollup Indices. It's a follow-up to https://github.com/elastic/kibana-team/issues/342.

Test cases being covered

• Shows system indices
  Shows Rollup Indices (After adding a mock rollup index) (Removed after finding out that we can't load the rollups plugin to test this. Covered by Functional Test.)
• Ensures all tabs are on home screen (Update to existing test)
• Close Index Test

[elasticmachine]

Pinging @elastic/kibana-stack-management (Team:Stack Management)

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 0110570
• Storybooks Preview

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
indexManagement	525.9KB	526.1KB	+117.0B

History

• 💔 Build #154808 failed a3c3e62
• 💔 Build #154778 failed a7c79e7
• 💔 Build #154712 failed d9305db
• 💔 Build #154442 failed 13eedbb
• 💚 Build #154046 succeeded f693a43

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

[yuliacech]

I think our current understanding of flaky tests is that we don't need to use nextTick() instead I think we put the setup() in an act() wrapper, similar to this:

await act(async () => {
    testBed = await setup();
});
const { component } = testBed;
component.update();

The code in Index Management is a bit older than in ILM, that is why there are still nextTcik() calls. But could you please update your new tests with this snippet?

[sebelga]

Yes, please please never use nextTick() anymore 👍

[yuliacech]

This code looks a bit confusing, I think that's because the context buttons don't have specific data-test-subj values. I suggest add a value in this file to use in the tests.

[yuliacech]

Thanks a lot for working on these tests, @cuff-links!
I left 2 comments, I think the one about nextTick could be great to fix before merging and the 2nd one is non-blocking for me.

[cuff-links]

This PR is closed in favor of #113692 and #114404 which address the same changes but splits them into their own PRs.