[RAC] Updates Alerts table cell actions

[claudiopro]

Summary

This PR fixes #111090 by

• Relabeling the Filter for value action to Filter in
• Adding a new Filter out action that excludes the given value from the query
  • This change is temporarily put on hold after discussion with @mgiota
• Removes cell actions from the Duration and Reason fields
• Removes the Copy to clipboard action from all cells

I'm also tweaking the label text to use sentence-style capitalization as recommended by EUI writing guidelines.

Known issues

• Clicking Filter in multiple times on the same value keeps adding to the query - this is already occurring in main and it is not regression.
• Filtering in and then out for the same value in this sequence creates an empty result set, while I assume filtering out should remove the previous filter instead.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[claudiopro]

Looks like the test ObservabilityApp Observability alerts Alerts table Cell actions "before each" hook for "Copy button works" is failing after the removal of the Copy buttton. I'll address it tomorrow.

The other test failure Uptime app with generated data When on the Synthetics Integration Policy Create Page create new policy allows saving when user enters a valid integration name and url/host doesn't seem related to this PR, maybe a flaky test? A rebase will hopefully address this.

[mgiota]

@claudiopro Good job! I'll put some comments directly in the line numbers.

Regarding failing tests yep uptime tests look irrelevant, so to update your PR just type @elasticmachine merge upstream in a comment (not sure if me typing this will re-run the PR, but in general you write above command and your PR re-runs or gets updated with latest master)

Regarding copy button failing tests, here's how you run them locally.

You first run the sever

node scripts/functional_tests_server --config x-pack/test/observability_functional/with_rac_write.config.ts

And then you run the tests:

node scripts/functional_test_runner --config x-pack/test/observability_functional/with_rac_write.config.ts --grep='Observability alerts'

(you can grep accordingly)

In order to link a PR with a Github issue you need to write fixes #issue_number. I updated your description accordingly (I renamed addresses to fixes)

[mgiota]

@claudiopro according to ACs duration should have only the expand icon. We should remove the filter in/out options for the duration column.

I want to comment regarding the issue you described when user filters in and then filters out the same value. I recommend we completely remove the Filter out functionality and properly implement it as part of this issue #116135, because now it looks broken and confusing. cc @katrin-freihofner @hbharding

[mgiota]

@claudiopro Here's an example of how you should label your PR #115171 once you open it for review

[claudiopro]

@mgiota postponing the implementation of the Filter out action until we implement the filter manager seems reasonable to me. After acquiring more context, I agree we should avoid shipping a brittle implementation.

[claudiopro]

@elasticmachine merge upstream

[mgiota]

LGTM!

[claudiopro]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 4905e31
• 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
observability	376.0KB	375.6KB	-481.0B
timelines	235.9KB	236.0KB	+49.0B
total			-432.0B

History

• 💚 Build #2692 succeeded 19efcd7
• 💔 Build #2511 failed 7cbc1c2
• 💔 Build #2411 failed b127d51
• 💔 Build #2226 failed 44462c6
• 💔 Build #2091 failed 70ea729
• 💔 Build #2078 failed 68a0e61

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

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	8.0

This backport PR will be merged automatically after passing CI.