tweak kontainer tests to reduce flake

[mantis-toboggan-md]

Summary

Fixes #17735

Occurred changes and/or fixed issues

This PR updates kontainer driver tests to remove a race condition. Instead of waiting for an Activating state in one driver before asserting an Activating state in another, which may have already progressed to Active, only the Active state is asserted in the bulk activation step.

The Activating -> Active status updates are still validated in the 'can create new driver' test

also in this pr:

• fixed invalid timeout in 'create new driver' test
• updated the delete driver test to use the action menu 'delete' option instead of re-testing the bulk action delete that is covered by another test
• updated the assertion in the delete driver test to fail when the driver is still present
• update activate driver test to ensure the example driver is actually inactive before the rest of the test runs
• update the deactivate driver test to assert that the driver is actually reported as deactivated

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
• The PR has been reviewed in terms of Accessibility
• The PR has considered, and if applicable tested with, the three Global Roles Admin, Standard User and User Base

[mantis-toboggan-md]

No check for Activating->Active status here because the driver may be updated to Active too quickly, introducing some flakiness

[marcelofukumoto]

Question
I think the LONG_TIMEOUT_OPT cannot be used on the .should.
That is for most of the cases here. Are you sure it is actually applying the timeout?
I faced this problem before. (And I think I still have similar codes not working)

I usually change to something like this.

    driversPage.list().details(exampleDriver, 1).contains('Active', LONG_TIMEOUT_OPT);

I am happy to discuss if you are not sure. I did some tests but we can check together.

[mantis-toboggan-md]

You're right, thanks for catching this! I got .should('contain' and .contains(... mixed up at some point. I updated the PR to use .should('contain'... instead. Given that the tests pass anyway maybe these two timeouts are not needed at all? I'm kind of inclined to keep them just to be cautious

[marcelofukumoto]

• Removed Activating will reduce the Flakiness but reduce one test as well (ideally). It is usually short lived so I can imagine how that improve flakiness.
• Verifying the state on the UI additionally makes it less flaky as well.
• Added timeout.

LGTM