Fixed alerting cypress tests.

[AWSHurneyt]

Description

Fixed cypress tests following PR opensearch-project/alerting#1612

Please backport this PR to 2.x, and 2.13 through 2.16.

Testing

Corresponding PR in the plugin repo that shows the tests pass with security disabled - opensearch-project/alerting-dashboards-plugin#1027

Ran the tests on a security enabled docker domain. Had to run some test suites in chunks as they were running slow on my local machine.

Issues Resolved

[List any issues this PR will resolve]

Check List

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[SuZhou-Joe]

Suppose the failure should be flaky, let me rerun the alerting test.

[AWSHurneyt]

@SuZhou-Joe Actually, could you remove the 2.13-2.15 backport labels? We don't need to backport these fixes that far. Sorry!

[SuZhou-Joe]

@AWSHurneyt Sure, but the bucket and query cases keep failing, do you know the reason?

[AWSHurneyt]

@SuZhou-Joe
@amsiglan ran the tests locally without security, and the screenshots above were run on a security-enabled docker image. They're passing reliably locally. Unsure what could be the difference in the PR execution.

[amsiglan]

@SuZhou-Joe @amsiglan ran the tests locally without security, and the screenshots above were run on a security-enabled docker image. They're passing reliably locally. Unsure what could be the difference in the PR execution.

@SuZhou-Joe I have seen in the past that CIs here fail but they are passing in our repo CIs as well as the release test passes, so I think we should be fine merging this change to unblock 2.16 and only spend time investigating if the auto cut issue is not resolved

[SuZhou-Joe]

@amsiglan @AWSHurneyt I see, I will take your manual sign-off to unblock the 2.16 release. Create an issue #1464 to track.