Fixed cypress memory failures.

[AWSHurneyt]

Description

1. Some cypress test specs were failing due to memory issues. Fixing those issues.

We detected that the Chrome Renderer process just crashed.

We have failed the current spec but will continue running the next spec.

This can happen for a number of different reasons.

If you're running lots of tests on a memory intense application.
  - Try increasing the CPU/memory on the machine you're running on.
  - Try enabling experimentalMemoryManagement in your config file.
  - Try lowering numTestsKeptInMemory in your config file during 'cypress open'.

You can learn more here:

https://on.cypress.io/renderer-process-crashed

2. Fixed some malformed test assets.
3. Removed developer comments.
4. Fixed some header styling for alerts dashboard, and monitor list pages.
5. Removed duplicate buttons on monitor list page.

Issues Resolved

[List any issues this PR will resolve]

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• 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.

[AWSHurneyt]

Removing this variable so the alerting backend can determine whichever version of OS core is needed to bring up a cluster.

[AWSHurneyt]

Bundling plugins separately as it could take 10+ minutes to bundle during the yarn start step. During that time, the localhost:5601 endpoint is reachable, but not accessible; it displays an error calling out that opensearch dashboards isn't ready.

[AWSHurneyt]

Fixing malformed sample monitor.

[AWSHurneyt]

Fixing malformed sample monitor.