Use smaller and compressed varients of buttons and form components

[AMoo-Miki]

Description

Replace instances of EuiButton that don't have an explicit sizing attribute to EuiSmallButton*.
Replace instances of Eui<form elements> that don't have density attributes to EuiCompressed<form elements>.
Add and use compressed to DateRangePicker and FrequencyPicker.

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]

@AMoo-Miki We have issue #415 to track known flaky cypress tests. Looks like the tests failing in this PR are not mentioned in that issue. I'm wondering whether the changes caused some kind of regression, or whether the tests just need to be refactored to reflect the changes.

Do they pass locally for you?

[AMoo-Miki]

@AMoo-Miki We have issue #415 to track known flaky cypress tests. Looks like the tests failing in this PR are not mentioned in that issue. I'm wondering whether the changes caused some kind of regression, or whether the tests just need to be refactored to reflect the changes.

Do they pass locally for you?

In one of the cases, the test starts populating the index pattern but is interrupted by the cluster being added to the page and then the index pattern is left blank.

• Query-Level Monitors > can have triggers > with names that contain periods

query_level_monitor_spec.js.mp4

• Query-Level Monitors > can be updated > to have multiple indices
  The same index pattern field is involved here too and while the video doesn't capture the interaction since it is below the viewport, the message indicates the cluster selection is causing trouble.

[AMoo-Miki]

Apparently, these have been failing for some time now: https://github.com/opensearch-project/alerting-dashboards-plugin/actions/workflows/cypress-workflow.yml

[AWSHurneyt]

The composite monitor spec does have a flaky test, but it looks like it passed in this PR from a few days ago. Which was the most recent merge to main before today.
https://github.com/opensearch-project/alerting-dashboards-plugin/pull/1004/checks

I'm rerunning the checks in PR 1010 now to see if maybe the tests are flaky.

[AMoo-Miki]

@AWSHurneyt The same 3 failed in https://github.com/opensearch-project/alerting-dashboards-plugin/actions/runs/10050410663/job/27778265636 which has no changes.

[opensearch-trigger-bot]

The backport to 2.16 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/alerting-dashboards-plugin/backport-2.16 2.16
# Navigate to the new working tree
pushd ../.worktrees/alerting-dashboards-plugin/backport-2.16
# Create a new branch
git switch --create backport-1010-to-2.16
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 cc8b95964616f23642ca88fc0564cb2fa3840eaf
# Push it to GitHub
git push --set-upstream origin backport-1010-to-2.16
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting-dashboards-plugin/backport-2.16

Then, create a pull request where the base branch is 2.16 and the compare/head branch is backport-1010-to-2.16.

[AWSHurneyt]

Auto backport to 2.16 failed. Will try to auto backport the 2.x PR (#1017).