…ic#190028)

## Summary

This PR is a precursor to elastic#189871,
as part of the spaces improvement initiative there's a need to be able
to share the user privilege assignment component between the roles
experience and the new spaces experience to prevent duplication of
business logic and cohesiveness in the privilege assignment experience.

The aforementioned PR extracts the required component into it's own
package so it might be consumed as needed, this PR is particularly
concerned with extracting business logic said UI component depends on
that exists still within the security plugin. For context; the security
plugin already depends on the spaces plugin, so having the spaces plugin
in turn statically depend on the security plugin creates a cyclic
dependency. That being said to complement the eventual state of said
component so it might be imported elsewhere outside of the security
plugin there's a need to extract further logic into standalone packages,
so that the spaces plugin can consume this plugin without the afore
mentioned cyclic dependency problem.


#### Visually; 

##### Problem;


![image](https://github.com/user-attachments/assets/6be85fb0-3ba3-4d5f-b614-3c0ff2cf7c69)

##### Proposal

![image](https://github.com/user-attachments/assets/5c4f423d-4ad4-48f4-b5bd-2ea0a99b196e)[^legend]

[^legend]: items marked in blue are the packages created in this PR,
whilst the entire diagram is the proposed future state

<!--### Checklist

Delete any items that are not applicable to this PR.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)


### 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&mdash;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&mdash;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](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |


### For maintainers

- [ ] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

…le on keyboard focus (elastic#187861)

Closes: elastic/observability-accessibility#43
Closes: elastic/observability-accessibility#18

## Description
- elastic/observability-accessibility#43: The
Observability Inventory map view has a grid of map tiles that each
accept a mouse event to show a tooltip. This tooltip must also be
available when the tile receives keyboard focus.

- elastic/observability-accessibility#18: The
Inventory > Kubernetes Pods popover stays open when I click "Create
Inventory Rule" and the modal dialog opens. This creates an odd stacking
order and obscures content for users at smaller viewport width.

## Steps to recreate
1. Open [Inventory Hosts map
view](https://keep-serverless-fyzdg-f07c50.kb.eu-west-1.aws.qa.elastic.cloud/app/metrics/inventory?inventoryViewId=%270%27&waffleFilter=(expression:%27%27,kind:kuery)&waffleTime=(currentTime:1719523489979,isAutoReloading:!f)&waffleOptions=(accountId:%27%27,autoBounds:!t,boundsOverride:(max:1,min:0),customMetrics:!(),customOptions:!(),groupBy:!(),legend:(palette:cool,reverseColors:!f,steps:10),metric:(type:cpu),nodeType:host,region:%27%27,sort:(by:name,direction:desc),timelineOpen:!f,view:map)&assetDetailsFlyout=(assetType:!n,detailsItemId:!n)&assetDetails=!n)
2. Change Hosts to Kubernetes Clusters
3. Try to select specific node using the keyboard 

## Screens


https://github.com/user-attachments/assets/9ab3b20d-1144-48ed-9760-363f43bafb4b



https://github.com/user-attachments/assets/e41bba9f-f3c5-4ce7-bba4-98cf26a2137a

…stic#190857)

## Summary

While investigating some issues with the alertsClient, I realized that
we weren't writing out any rule information for the logged messages.
This made debugging quite difficult, as I wanted to see the rule, so had
to search through the alerts indices for the specified alert to get it's
rule id, rule type, etc.

As an example, see elastic#190376

This PR adds that kind of rule info to the logged messages in
alertsClient, as well as the typical sort of tags we write out (rule id,
rule type, module).

… hosts list (elastic#191063)

Closes [elastic#190418](elastic#190418)

## Summary

This PR adds a popover for the hosts that are not monitored by the
system integration to help users troubleshoot the problem

## Testing 

A way to check it is to have a host that is monitored by system
integration (I am using metricbeat) and sythtrace hosts - there we
should have both (I am using `node scripts/synthtrace
infra_hosts_with_apm_hosts --scenarioOpts.numInstances=50 --live`)

- Go to hosts view and check the table
- The hosts that are **not** monitored by the system integration should
have an icon before the host name which opens the popover with some
explanation and documentation links
- The hosts that are monitored by the system integration should not have
an icon before the host name

<img width="961" alt="Screenshot 2024-08-22 at 12 02 27"
src="https://github.com/user-attachments/assets/a3330f3f-33df-41ae-8135-71aea98e2660">


![image](https://github.com/user-attachments/assets/b28474d4-2272-4372-b70d-6370aa8e2a9d)

…acity based claiming (elastic#189431)

Resolves elastic#189111

## Summary

Adds jest integration test to test cost capacity based claiming with the
`mget` claim strategy. Using this integration test, we can exclude
running other tasks other than our test types. We register a normal cost
task and an XL cost task. We test both that we can claim tasks up to
100% capacity and that we will stop claiming tasks if the next task puts
us over capacity, even if that means we're leaving capacity on the
table.

---------

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

)

## Summary

Settings add config to enable default rules !!

separated out of elastic#186585 !!

<img width="1725" alt="image"
src="https://github.com/user-attachments/assets/3fc18d13-d0fe-4f08-8e19-ae43fcb83228">

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Dominique Belcher <dominique.clarke@elastic.co>

## Summary

Using plural from `react-intl` in the Session View for `Show N alerts`
text

- part of elastic/security-team#10316
- fixes elastic#189880

…tic#191080)

## Summary

It ain't much but it's honest work

- fixes elastic#181641
- part pf elastic/security-team#10316

## Screencast
tbh before is not as bad as in the linked ticket, so we can also leave
it as it is until we do responsiveness on this page properly.

before


[screencast-localhost_5601-2024.08.22-15_14_34.webm](https://github.com/user-attachments/assets/4f119203-6a91-4a52-9514-3489789649ce)

after


[screencast-localhost_5601-2024.08.22-15_05_32.webm](https://github.com/user-attachments/assets/36276e71-8d2d-4095-b2b6-e5524f6d0692)

… if no assignees exist (elastic#190937)

## Summary

Addresses elastic#177864

Disables the unassign alert action if no assignees exist.

…t data source (elastic#190438)

## Summary

Implements elastic/logs-dev#169.

This uses the new central log sources setting as the default data source
in the Logs Explorer. The `AllSelection` is now amended to use a set of
indices, this `AllSelection` can be defined by the consumer (or falls
back to a default). In the case of the Observability Logs Explorer this
value is resolved from the setting and used as the `AllSelection` passed
to the Logs Explorer controller.

Automated by
https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/1136

## Summary

Epic link: elastic/kibana-team#785

The Spaces Management `SectionPanel` component has been updated to make
`title` an optional prop. This PR takes a small change out of a larger
PR to be delivered next: elastic#184697.

Currently, `title` is shown consistently for all `SectionPanel` elements
in the Edit Space screen. In the new design, the panels will appear on a
tabbed interface. Observe how the new design implemented in the
larger/next PR will leave the `SectionPanel` title empty (this
screenshot was taken when running Kibana in the branch for the next PR):
<img width="1076" alt="image"
src="https://github.com/user-attachments/assets/ba2d70f0-e8be-4885-bc2b-17e5cd3bdf9d">

The current design will still be used for the Create Space interface. As
a reminder, here is how the current design looks:
<img width="945" alt="image"
src="https://github.com/user-attachments/assets/4009bbfc-20fd-41cd-b89f-14bb52be4522">

## Summary

This PR moves code that is usually impacted by a Puppeteer/Chromium
upgrade to a package. The same work is happening to a lesser degree in
the 7.17 branch. Together, these changes will ease the manual labor of
backporting the upgrades from main to 7.17.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

Automated by
https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/1147

This PR updates the function definitions and inline docs based on the
latest metadata from Elasticsearch.

…190999)

Refactor control group settings tests
1. move non-functional test cases to unit tests
2. use pre-built dashboard to avoid time of building dashboard in test

### Before
Tests take 4 minutes to run locally
<img width="400" alt="Screenshot 2024-08-21 at 3 12 31 PM"
src="https://github.com/user-attachments/assets/96cf584c-2b32-4281-86ee-9791544bd5fa">


### After
Tests take 1 minute to run locally
<img width="400" alt="Screenshot 2024-08-21 at 2 53 37 PM"
src="https://github.com/user-attachments/assets/853a6f3a-74c5-4ca8-a488-99dd24477b1e">

---------

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

## Summary

**NOTE** I will need help testing this before we merge it!

I spoke with @spong about an upcoming PR we have here:
elastic#190426 which bumps the langgraph
version from 0.0.31 to 0.0.34, unfortunately this caused a lot of type
errors in the default assistant.

After some more discussion we proposed to open a PR that removes some of
the more complex layers and to fix up the type issues. Though I have not
worked on this graph before, the changes hopefully makes sense 👍

Graph flow:

![image](https://github.com/user-attachments/assets/911190c1-2cdc-429f-bd1b-2b4a6a343729)


The PR changes the below items to remove some of the abstractions and
resolve some of the type issues, also adds a few improvements in
general:

- Moves `llmType`, `bedrockChatEnabled`, `isStream` and `conversationId`
to be invoke parameters rather than compile parameters. This allows them
to be used in state, and removes the need to pass them everywhere as
parameters. Adding them to the state also allows them to be available in
langsmith.
- Removes the constants defining each node with wrappers and rather
expose them directly as async functions. This removes a lot of the
boilerplate code and it makes reading the stacktraces much easier.
- Moved to a single `stepRouter` used for the current conditional edges.
This allows one to very easily extend the routing between either
existing or new nodes, and makes it much easier to understand what
conditions are routed where.
- Exports a common `NodeType` object constant (no need for the extra
compile overhead of Enums here, we are only using strings), to make the
node name strings auto-complete and prevent hardcoded names for the
router.
- Added a `modelInput` node to be the starter node. This was first
because adding nodes inside if conditions usually create errors, so it
was created to be able to set the `hasRespondStep` state. However this
node is nice to have as an entrypoint in which you find yourself wanting
to change the state based on the invoke parameters or other conditions
retrieved from other parts of the stack etc before it continues to any
of the other nodes.
- Added a `yarn draw-graph` command, that outputs to
`docs/img/default_assistant_graph.png`. This is then also included in
the readme. This makes it better for changes by other teams (like me) to
understand the intended graph workflows easier.


### Checklist

Delete any items that are not applicable to this PR.

- [x]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials

### For maintainers

- [x] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

---------

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

## Summary

Close elastic/elasticsearch#111544

Follow-on to elastic/elasticsearch#111544

## Summary

Due to a [recent change](elastic#188495)
on the UnifiedDataTable component, the density was set to default to
`compact`. This PR overrides this property to `expanded` in order to
keep consistency with the Design specs.

## Screenshot

### Before PR changes:


![image](https://github.com/user-attachments/assets/329673ae-31f6-42f0-8552-253dbd465a7f)

### After PR changes:


![image](https://github.com/user-attachments/assets/bf9d9930-25e6-40a5-9639-a691d9d56893)


### Design spec


![image](https://github.com/user-attachments/assets/5f6ab4f8-807c-4e4c-a89e-56359493e4b2)

Generated by
https://buildkite.com/elastic/kibana-api-docs-daily/builds/808

…1130)

## Summary

This PR is to address issue where whenever user tries to check on the
field on the field selector outside the 1st page, user will be navigated
to the 1st page upon checking the checkbox.


https://github.com/user-attachments/assets/89375c54-deac-49a7-a3a1-2a4d5745ccc7

Steps to test:
- Get some findings data in
- Navigate to Findings Page
- Group by None
- Click on Fields selector, navigate to other pages 
- Check on any of field checkboxes

Expected Result:
User should not get navigated back to page 1

…logs-only' view (elastic#191108)

closes elastic#190437
Before:
<img width="1652" alt="Screenshot 2024-08-22 at 16 54 39"
src="https://github.com/user-attachments/assets/ed501a53-b715-49b3-b382-a1d0f9861275">

After:
<img width="1644" alt="Screenshot 2024-08-22 at 16 55 25"
src="https://github.com/user-attachments/assets/6b73a5d7-9747-4951-8ea6-1b4200a73313">
<img width="1692" alt="Screenshot 2024-08-22 at 16 55 43"
src="https://github.com/user-attachments/assets/e3cb3d55-87e3-4515-b4f9-c1fddcd8ce4d">

…tic#190814)

## Summary

We wanted to remove the APM link from the hosts and containers flyout.

|Entity|Before|After|
|-|-|-|
|Host|<img
src="https://github.com/user-attachments/assets/3a894875-d76c-4776-b9c0-06e793330071"
width="330"/>|<img
src="https://github.com/user-attachments/assets/e39e5b0f-0491-478b-b3c8-75656fabb8ee"
width="330"/>|
|Container|<img
src="https://github.com/user-attachments/assets/d0d8dce8-3653-451f-b812-0a8c90758529"
width="330"/>|<img
src="https://github.com/user-attachments/assets/fb167ee8-294e-406c-9475-964b9c05b009"
width="330"/>|

## Summary

Decrease the accordion title and code block content within the log
overview tab.

------

The content in the log overview tab of the doc viewer flyout was large
relative to surrounding UI elements (see below). The changes in this PR
make it more consistent with other sections of the page.

**Before**
<img
src="https://github.com/user-attachments/assets/521356d6-1170-47fb-9931-34072296fc7e"
width="420" />


**After**
<img
src="https://github.com/user-attachments/assets/51922e37-94a2-4f00-80fa-8202069717fc"
width="420" />

_Font sizes now comparable to those used in and around the data grid,
for example._

![CleanShot 2024-08-21 at 21 55
23@2x](https://github.com/user-attachments/assets/32f06022-b9aa-4211-8cb6-01bc44abfbad)

### Checklist


Delete any items that are not applicable to this PR.

- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

…pec generation (elastic#190840)

## Summary

- Removes `apidoc-markdown` dependency and custom scripts for generating
internal documentation for ML Kibana endpoints
- Replaces apidoc annotations with `summary` and `description` props for
route handlers and kbn-schemas to generate an OpenAPI spec file
- `/internal/ml/jobs/delete_jobs` route was not versioned for some
reason, I changed that


#### How to test 

1. Enable OAS endpoint in `kibana.dev.yml`

```yaml
server.oas.enabled: true
```
2. Start Kibana dev server 
```bash
yarn start --no-base-path
```
3. Call the OAS endpoint for ML _internal_ routes 
```bash
curl -s -u <USERNAME>:<PASSWORD> http://localhost:5601/api/oas\?pathStartsWith\=/internal/ml\&access\=internal -o ml_kibana_openapi.json
```

…ns (elastic#191115)

## Summary

This PR removes the deprecated `squid` integration based on the Filebeat
module (deprecation issue
[here](elastic/beats#37746)). Instead, as of
now, a user that wants to use the `squad` integration needs to tick the
`Display beta integrations` and install the "new" squid integration


### Risk Matrix

N/A


### For maintainers

- [ ] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

Automated by
https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/1155

…astic#190426)

## Summary

This PR prepares the ECS Mapping graph to support larger samples by
chunking and running certain parts of the graph concurrently side by
side and merging the results rather than trying to use one large
context.

More details below, but in general there is only a slight modification
to the actual code, most of the lines are related to moving code around
to new files and updated tests.

There are also some minor tweaks to the ECS graph code in general, below
is the related changes:

1. Moved some code out of graph.ts to make it a bit smaller (moved
model* functions to a new model.ts, moved state to its own file.
2. Added chunkSize as a optional input to the graph (default to 10
fields with an actual string value per chunk). Just to allow it to be
overwritten if necessary later.
3. Renamed the `samples` state to `prefixedSamples` and
`formattedSamples` to `combinedSamples` as it got really confusing at
some point when debugging. I also updated the function argument names
that used them to the new names to better understand which sample type
they are using.
4. Renamed `modifySamples` to `prefixSamples` to clarify what it
actually modifies
5. Moved `mapping`, `invalid`, `duplicate`, `missing` and `validate`
nodes to its own subgraph. The `combinedSamples` state is now set when
invoking the subgraph, the value will be its related `chunk`, so it only
needs to work on this smaller subset of data.
6. The `currentMapping` state is now only used by the sub graph, once
all the subgraphs has finished, the will post their own results to
`finalMapping` state. This state uses a reducer function, that combines
the existing state with the new, so all results from the X subgraphs
running will be merged into the same resulting object as before this PR.

### Checklist

Delete any items that are not applicable to this PR.

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios


### For maintainers

- [x] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

Fixes elastic/observability-accessibility#54

## How to test
- Turn on your Screen Reader (voiceOver on MAC)
- Go to SLO detail page
- The burn rate abbreviation labels should be `1 hour`, `6 hours`, `24
hours`, `72 hours`
- Navigate with `Tab` button to the burn rate time range abbreviations
- The Screen Reader should speak out `1 hour`, `6 hours`, `24 hours`,
`72 hours`




https://github.com/user-attachments/assets/4cc6a375-afef-4531-a177-d52e9326a701

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

## Summary

Scaffolding empty plugin for development of day 0 onboarding work. This
plugin is currently disabled by default and will be enabled for ES3 when
it's ready for users.

## Summary

Summarize your PR. If it involves visual changes include a screenshot or
gif.

If go to CSPM page and click save and continue, the Cloud Formation Pop
occasionally flickers and shows Fleet Server host error for one second.
This PR adds a boolean `isLoadingIntialRequest` for us to wait after
loading Fleet Server hosts before showing the errors.

[Quick Wins](elastic/security-team#10316)

Locally:

https://github.com/user-attachments/assets/bf393103-9d21-4ddf-96a9-8fc3e9626369

Serverless QA


https://github.com/user-attachments/assets/d1877a5a-97ba-4ce6-b87b-177656bdd004

## Summary

Adds @elena-shostak to the Iron Bank hardening manifest.

…ic#191135)

## Summary

Resolves
elastic/observability-accessibility#14

### Testing

1. Turn on your screen reader. For Mac, to turn on voiceover it's
Command + F5.
2. Make sure you have a few synthetics monitors created, at least two
3. Navigate to `synthetics/add-monitor`. Tab to monitor type radio list
and use the right and left arrow buttons to change the option.
4. The content of the bottom descriptive callout should be read when
changing the monitor type

Fixes deprecation warnings e.g.
https://github.com/elastic/kibana/actions/runs/10479478609.

The only breaking change is the Node.js version, which is already being
overriden. See
https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/

https://github.com/github/codeql-action/blob/main/CHANGELOG.md

…188881)

Adds enforcement for the global time filter to limit the min refresh interval.

Since the Search team wrote this API and has the most context into the
feature, we are transferring ownership from the AppEx Management team to
Search.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com>

…lastic#190690)

## Summary

This PR enforces ESLint rules in FTR tests, in particular:
- `no-floating-promises` rule to catch unawaited Promises in
tests/services/page objects

_Why is it important?_
- Keep correct test execution order: cleanup code may run before the
async operation is completed, leading to unexpected behavior in
subsequent tests
- Accurate test results: If a test completes before an async operation
(e.g., API request) has finished, Mocha might report the test as passed
or failed based on incomplete context.
```
198:11  error  Promises must be awaited, end with a call to .catch, end with a call to .then
with a rejection handler or be explicitly marked as ignored with the `void` operator 
@typescript-eslint/no-floating-promises
```
<img width="716" alt="Screenshot 2024-08-20 at 14 04 43"
src="https://github.com/user-attachments/assets/9afffe4c-4b51-4790-964c-c44a76baed1e">

- recommended rules from
[eslint-mocha-plugin](https://www.npmjs.com/package/eslint-plugin-mocha)
including:
-
[no-async-describe](https://github.com/lo1tuma/eslint-plugin-mocha/blob/main/docs/rules/no-async-describe.md)
-
[no-identical-title.md](https://github.com/lo1tuma/eslint-plugin-mocha/blob/main/docs/rules/no-identical-title.md)
-
[no-sibling-hooks.md](https://github.com/lo1tuma/eslint-plugin-mocha/blob/main/docs/rules/no-sibling-hooks.md)
and others

Note for reviewers: some tests were skipped due to failures after
missing `await` was added. Most likely is a "false positive" case when
test is finished before async operation is actually completed. Please
work on fixing and re-enabling it

---------

Co-authored-by: Tiago Costa <tiago.costa@elastic.co>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

## Summary

Resolves elastic#172033

### Release note
Enables wildcard search for the Synthetics waterfall chart.

### Testing

1. Create a browser monitor
2. Navigate to the waterfall chart
3. Add a wildcard search in the text box. For example `*.js`. 
4. You shouldn't see an error, and it should match all requests with
`.js` in the name

…lastic#191104)

Closes elastic#190523 
## Summary

This PR provides troubleshooting information in the services section on
the host details page.

## Testing
Go to the hosts details page / host flyout
- using a host without services monitored with system integration

![image](https://github.com/user-attachments/assets/5226e4a1-7b19-4a22-b11d-2aae55f543e3)

- using a host without services not monitored with system integration (
only detected by APM )

![image](https://github.com/user-attachments/assets/f63513bd-d3f9-41eb-97a6-0011b2d11673)

- icon next to the title (same as the table)
<img width="1690" alt="image"
src="https://github.com/user-attachments/assets/b722b61d-29d0-46dd-a3d8-e9f594236bf1">


For hosts with services, nothing changes (the service is shown): 
<img width="474" alt="image"
src="https://github.com/user-attachments/assets/81f54a1a-485d-4e0b-a746-618fca5a864c">

## Summary

Part of elastic#189662

## Suggests comma and pipe


https://github.com/user-attachments/assets/c09bc6fd-20a6-4f42-a871-c70e68e6d81a

## Doesn't suggest comma when there are no more fields


https://github.com/user-attachments/assets/29fce13e-e58b-4d93-bce5-6b1f913b4d92

## Doesn't work for escaped columns :(


https://github.com/user-attachments/assets/3d65f3b9-923d-4c0e-9c50-51dd83115c8b

As part of this effort I discovered
elastic#191100 and
elastic#191105, as well as a problem
with column name validation (see
elastic#177699)

I think we can revisit column escaping and probably resolve all of these
issues (issue [here](elastic#191111)).


### Checklist

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>

…90378)

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>
Co-authored-by: Walter Rafelsberger <walter.rafelsberger@elastic.co>

)

## Summary

This adds an aria-label for an icon button, and fixes a warning with a
button nesting inside a button.

## Summary

Changes in this PR include:

_Slight adjustment to search bar spacing (`gap`) on..._
- Index Management > Indices (tab)
- Management > Index templates (tab)
- Rules > Logs
- Connectors > Logs

_Fix search input to be full width, as intended on..._
- Connectors > Logs (now matches Rules > Logs)

**Before and after**

![CleanShot 2024-08-22 at 13 59
12@2x](https://github.com/user-attachments/assets/f5343d4d-10fa-4b44-a727-1bc98f916016)



### Checklist

Delete any items that are not applicable to this PR.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)


### 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](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |


### For maintainers

- [ ] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

## Summary

Resolves
elastic/observability-accessibility#68

Adjusts headings levels on the Monitor Add/Edit page.

Note, the `Observability` heading is out of scope

<img width="1694" alt="Screenshot 2024-08-23 at 9 44 33 AM"
src="https://github.com/user-attachments/assets/53eb72cb-28ff-43d8-9037-0853525e8228">

towards: elastic#189306

This PR fixes the `Deleting current node has failed.`errors mentioned in
the above issue.

…lastic#191140)

## Summary

Resolves
elastic/observability-accessibility#33

### Testing

1. Turn on your screen reader. For Mac, to turn on voiceover it's
Command + F5.
2. Make sure you have a few synthetics monitors created, at least two
3. Navigate to `synthetics/management`. Tab through the monitor list
until you arrive at the edit, clone, and delete buttons
4. The label spoken out on the screen reader should indicate which
monitor you are taking action on, with statements such as "Delete
monitor X", "Clone monitor X" and "Edit monitor X"

## Summary

With elastic/elasticsearch#111712,
Elasticsearch is again erroring when an index is missing. So, we can
unskip the test.

…t folder (elastic#190107)

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
|
[geckodriver](https://togithub.com/webdriverio-community/node-geckodriver)
| devDependencies | patch | [`^4.4.2` ->
`^4.4.3`](https://renovatebot.com/diffs/npm/geckodriver/4.4.2/4.4.3) |

---

### Release Notes

<details>
<summary>webdriverio-community/node-geckodriver (geckodriver)</summary>

###
[`v4.4.3`](https://togithub.com/webdriverio-community/node-geckodriver/releases/tag/v4.4.3):
Release 4.4.3

[Compare
Source](https://togithub.com/webdriverio-community/node-geckodriver/compare/v4.4.2...v4.4.3)

- when if connectExisting passed to driver then args shouldn't include
websocketPort
([#&elastic#8203;509](https://togithub.com/webdriverio-community/node-geckodriver/issues/509))
([`a4acdea`](https://togithub.com/webdriverio-community/node-geckodriver/commit/a4acdea))
- chore: update deps
([`8cc5bb7`](https://togithub.com/webdriverio-community/node-geckodriver/commit/8cc5bb7))
- chore(deps-dev): bump
[@&elastic#8203;types/node](https://togithub.com/types/node) from 22.1.0 to
22.2.0
([#&elastic#8203;512](https://togithub.com/webdriverio-community/node-geckodriver/issues/512))
([`868fe28`](https://togithub.com/webdriverio-community/node-geckodriver/commit/868fe28))
- chore(deps-dev): bump webdriverio from 8.39.1 to 8.40.2
([#&elastic#8203;513](https://togithub.com/webdriverio-community/node-geckodriver/issues/513))
([`9fdecb6`](https://togithub.com/webdriverio-community/node-geckodriver/commit/9fdecb6))
- chore(deps-dev): bump tsx from 4.16.5 to 4.17.0
([#&elastic#8203;511](https://togithub.com/webdriverio-community/node-geckodriver/issues/511))
([`a7d2b5b`](https://togithub.com/webdriverio-community/node-geckodriver/commit/a7d2b5b))
- chore(deps-dev): bump tsx from 4.16.2 to 4.16.5
([#&elastic#8203;506](https://togithub.com/webdriverio-community/node-geckodriver/issues/506))
([`c8254cd`](https://togithub.com/webdriverio-community/node-geckodriver/commit/c8254cd))
- chore(deps-dev): bump husky from 9.1.3 to 9.1.4
([#&elastic#8203;508](https://togithub.com/webdriverio-community/node-geckodriver/issues/508))
([`3999a09`](https://togithub.com/webdriverio-community/node-geckodriver/commit/3999a09))
- chore(deps): bump [@&elastic#8203;zip](https://togithub.com/zip).js/zip.js
from 2.7.47 to 2.7.48
([#&elastic#8203;505](https://togithub.com/webdriverio-community/node-geckodriver/issues/505))
([`d30131f`](https://togithub.com/webdriverio-community/node-geckodriver/commit/d30131f))
- chore(deps-dev): bump
[@&elastic#8203;vitest/coverage-v8](https://togithub.com/vitest/coverage-v8)
from 2.0.4 to 2.0.5
([#&elastic#8203;504](https://togithub.com/webdriverio-community/node-geckodriver/issues/504))
([`b56d045`](https://togithub.com/webdriverio-community/node-geckodriver/commit/b56d045))
- chore(deps-dev): bump
[@&elastic#8203;typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
from 7.17.0 to 7.18.0
([#&elastic#8203;507](https://togithub.com/webdriverio-community/node-geckodriver/issues/507))
([`4d9effd`](https://togithub.com/webdriverio-community/node-geckodriver/commit/4d9effd))
- chore(deps-dev): bump
[@&elastic#8203;types/node](https://togithub.com/types/node) from 22.0.0 to
22.1.0
([#&elastic#8203;503](https://togithub.com/webdriverio-community/node-geckodriver/issues/503))
([`7a30e84`](https://togithub.com/webdriverio-community/node-geckodriver/commit/7a30e84))
- chore(deps-dev): bump
[@&elastic#8203;typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
([#&elastic#8203;500](https://togithub.com/webdriverio-community/node-geckodriver/issues/500))
([`32f98a9`](https://togithub.com/webdriverio-community/node-geckodriver/commit/32f98a9))
- chore(deps-dev): bump
[@&elastic#8203;vitest/coverage-v8](https://togithub.com/vitest/coverage-v8)
from 2.0.3 to 2.0.4
([#&elastic#8203;497](https://togithub.com/webdriverio-community/node-geckodriver/issues/497))
([`5ca67e1`](https://togithub.com/webdriverio-community/node-geckodriver/commit/5ca67e1))
- chore(deps-dev): bump
[@&elastic#8203;typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
from 7.16.1 to 7.17.0
([#&elastic#8203;501](https://togithub.com/webdriverio-community/node-geckodriver/issues/501))
([`7790925`](https://togithub.com/webdriverio-community/node-geckodriver/commit/7790925))
- chore(deps-dev): bump typescript from 5.5.3 to 5.5.4
([#&elastic#8203;499](https://togithub.com/webdriverio-community/node-geckodriver/issues/499))
([`7a63544`](https://togithub.com/webdriverio-community/node-geckodriver/commit/7a63544))
- chore(deps-dev): bump eslint-plugin-unicorn from 54.0.0 to 55.0.0
([#&elastic#8203;496](https://togithub.com/webdriverio-community/node-geckodriver/issues/496))
([`82aa202`](https://togithub.com/webdriverio-community/node-geckodriver/commit/82aa202))
- chore(deps-dev): bump
[@&elastic#8203;types/node](https://togithub.com/types/node) from 20.14.11 to
22.0.0
([#&elastic#8203;498](https://togithub.com/webdriverio-community/node-geckodriver/issues/498))
([`b20e88c`](https://togithub.com/webdriverio-community/node-geckodriver/commit/b20e88c))
- chore(deps-dev): bump husky from 9.1.1 to 9.1.3
([#&elastic#8203;495](https://togithub.com/webdriverio-community/node-geckodriver/issues/495))
([`732d85f`](https://togithub.com/webdriverio-community/node-geckodriver/commit/732d85f))
- chore(deps-dev): bump
[@&elastic#8203;vitest/coverage-v8](https://togithub.com/vitest/coverage-v8)
from 2.0.2 to 2.0.3
([#&elastic#8203;493](https://togithub.com/webdriverio-community/node-geckodriver/issues/493))
([`1c2dbfd`](https://togithub.com/webdriverio-community/node-geckodriver/commit/1c2dbfd))
- chore(deps-dev): bump
[@&elastic#8203;typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
([#&elastic#8203;489](https://togithub.com/webdriverio-community/node-geckodriver/issues/489))
([`0b3994e`](https://togithub.com/webdriverio-community/node-geckodriver/commit/0b3994e))
- chore(deps-dev): bump husky from 9.0.11 to 9.1.1
([#&elastic#8203;494](https://togithub.com/webdriverio-community/node-geckodriver/issues/494))
([`255bbe4`](https://togithub.com/webdriverio-community/node-geckodriver/commit/255bbe4))
- chore(deps-dev): bump
[@&elastic#8203;types/node](https://togithub.com/types/node) from 20.14.10 to
20.14.11
([#&elastic#8203;490](https://togithub.com/webdriverio-community/node-geckodriver/issues/490))
([`f6c3d0f`](https://togithub.com/webdriverio-community/node-geckodriver/commit/f6c3d0f))
- chore(deps-dev): bump
[@&elastic#8203;typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
from 7.16.0 to 7.16.1
([#&elastic#8203;491](https://togithub.com/webdriverio-community/node-geckodriver/issues/491))
([`1492416`](https://togithub.com/webdriverio-community/node-geckodriver/commit/1492416))
- chore(deps): bump [@&elastic#8203;zip](https://togithub.com/zip).js/zip.js
from 2.7.45 to 2.7.47
([#&elastic#8203;492](https://togithub.com/webdriverio-community/node-geckodriver/issues/492))
([`a150be9`](https://togithub.com/webdriverio-community/node-geckodriver/commit/a150be9))
- chore(deps-dev): bump
[@&elastic#8203;types/node](https://togithub.com/types/node) from 20.14.9 to
20.14.10
([#&elastic#8203;480](https://togithub.com/webdriverio-community/node-geckodriver/issues/480))
([`016be65`](https://togithub.com/webdriverio-community/node-geckodriver/commit/016be65))

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Renovate
Bot](https://togithub.com/renovatebot/renovate).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjUuMSIsInVwZGF0ZWRJblZlciI6IjM3LjQyNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==-->

---------

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
Co-authored-by: Jonathan Budzenski <jon@elastic.co>

…191103)

Related to elastic#183220

## Summary

This PR saves ECS keyword group by fields in AAD document for ES query
rule.

|Rule|Before|After|
|---|---|---|

|![image](https://github.com/user-attachments/assets/0ba8699d-44bf-4930-b3f0-33b4ed8a7e0c)|![image](https://github.com/user-attachments/assets/a98d70e5-213e-4dc3-93a7-fa509828d15b)|![image](https://github.com/user-attachments/assets/00a57945-1590-4286-8132-072e19d5866f)|

|![image](https://github.com/user-attachments/assets/8fe39de4-97ac-4a66-8c69-5c2b552b8264)|![image](https://github.com/user-attachments/assets/9f3ec653-fa11-45cc-add0-d1923e68547e)|![image](https://github.com/user-attachments/assets/41ce2028-54f0-4ca4-8d63-0d371819865f)|

### How to test
- Create some data with ECS fields
- For example, you can use synthtrace command: `node scripts/synthtrace
simple_trace.ts --local --live`
- Create an ES Query rule grouped by ECS and non-ECS fields
- In the generated alert, you should be able to see the ECS group by
field but not the no-ECS ones

…lastic#191150)

## Summary

This PR addresses the following:

- Handling errors when creating Detection rules
- Handling errors when muting/unmuting Benchmark rules
- Handling Alerts pending on loading state when the user doesn't have
read permission to the Detection Rules alerts index
(`.alerts-security.alerts-default`).
- Centralized benchmark rules mutation success/error logic in the
`useChangeCspRuleState` hook.
- Fixed benchmark mute API that was disabling only one detection rule
per benchmark rule.


## Recordings

### Read Only User (Without .alerts-security.alerts-default read
permission)


https://github.com/user-attachments/assets/bbf153f8-2e33-4449-a25e-7bdf52e45275

### Read Only User (With .alerts-security.alerts-default read
permission)


https://github.com/user-attachments/assets/c4b69043-ab97-485b-8fdb-17245c44d48b

### Write permission user


https://github.com/user-attachments/assets/954c8b5e-0046-4e7e-a401-787e1b7eb211

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

…tic#190183)

This PR is the final step needed for us to re-enable pointer compression
on serverless.

It introduces a cli later used in a CI check that will prevent the
addition of new native modules on production as discussed and agreed
with Luke and Brandon previously.

It also removes the usages of `cbor-x` and replaces those with a
wrapping package `@kbn/cbor` which relies on the implementation coming
from `borc` with no native modules involved.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

…-cli/integration_tests/__fixtures__

Generated by
https://buildkite.com/elastic/kibana-api-docs-daily/builds/809

…#191239)

## Summary

This PR skips the failing serverless discover and visualize tests for
MKI runs.

For more details, see the corresponding issues elastic#191237 and elastic#191238.

Generated by
https://buildkite.com/elastic/kibana-api-docs-daily/builds/810

Generated by
https://buildkite.com/elastic/kibana-api-docs-daily/builds/811

Closes elastic#190892

Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>

)

Closes elastic#189383

## Summary

In 8.14.0 we added and enabled feature flag
`enablePackagesStateMachine`. This PR cleans it up as it's been enabled
since then and we don't need it anymore. Also removing related test
cases.

### Checklist

- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

---------

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

Closes elastic#189867

#### Summary

This PR improves the use of synthtrace as data generator for infra
functional test

#### What was done

- update `host.ts` in infra synthtrace client, so it can accept `cpu`
value as a param, added `core` metrics and the option to create a k8s
node same as a pod
- added `k8snode` entity to synthtrace client
- created `uninstallSystemPackage` method to
`infra_synthtrace_kibana_client`
- created a getter for the logs ES client in the test utils
- update and fix infra funtional tests

#### TODO in follow-up

- remove the use of archives
- get processes data also with synthtrace
- create alerts data with synthtrace

Issue elastic#186907.

Now even on wide screens, and when there is space after the last column,
a grey area is not shown, last column extended to meet the full page
width. We should extend the last column to meet the full page width.

![Screenshot 2024-08-23 at 14 38
50](https://github.com/user-attachments/assets/d62151fc-9640-46a8-ba60-2b9bd55deeae)


For this part of the task: "Also, we should consider adding a column
action for users to be able to reset the width of the column" I'll
create another issue.

How to test:
1. Create a rule, which will trigger alerts.
2. Go to Alerts table
3. Keep only 3-4 fields in the table
4. Check if the grey area after last field does not exist

![Screenshot 2024-08-23 at 14 42
00](https://github.com/user-attachments/assets/dd0eafb8-9261-4180-9829-eecc1685c04f)

### Checklist

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

## Summary

Closes elastic#190416

Hides the menu when there is no data.

## Summary

Fixing and improving a few things I noticed while discovering / ramping
up on the existing code
- address some nits
- extract / reuse some low level functions
- move things around
- add unit tests

addresses elastic#190964

Second in the series of PRs to address general DQD tech debt. Currently
this PR build on the work of
elastic#190970.

So this PR restructures components to colocate component throughout the
hierarchy.

So instead of:

```bash
root/
  component1/
  childOfComponent1/
  grandChildOfComponent1/
  component2/
  use_hook_used_for_1/
  use_hook_used_for_2/
```

we use:

```bash
root/
  component1/
    hooks/
      use_hook_used_for_1/
    childOfComponent1/
      grandChildOfComponent1/
  component2/
    hooks/
      use_hook_used_for_2/
```

PROs of such scaffold:
- complete and clear hierarchical visibility into component structure of
the entire DQD codebase
- ability to easily introduce and integrate a new change and calculate
its impact on the tree of components
- ability to easily remove colocated functionality without having to
scout through the convoluted DQD code
- clear understanding of where shared code should live as opposed to
know when its shoved into top level by default with other non shared
code
- since nesting too deep has an import name readability tax it forces us
to think about not splitting our components into too many small parts
but rather keep it balanced, as opposed to now where flat structure
incentivizes free and cheap fragmentation as seen with component like
<body />.

CONS:

- import names have too many `../../../../../../../../../`. It is
fixable by ts paths/webpack aliases, but on the other hand especially if
there are many of those it's an indication of potential architectural
smell, that needs to be addressed (which is a PRO).

Imho, overall visibility trumps any cons and facilitates greater ease of
adding new and changing existing functionality with more confidence.

## Before

![image](https://github.com/user-attachments/assets/89062883-c40a-410d-af43-8dbe3e712475)

## After

![image](https://github.com/user-attachments/assets/83e33a85-cf3e-4cb1-a56d-c7f4f27a1f37)

…rn More) (elastic#191072)

Part of:
https://github.com/elastic/observability-accessibility/issues/129

This PR addresses only the 'Learn More' section of the reported issue.
The issue concerning the `Copy` button will be addressed first on the
EUI side.

# What was changed: 

1. `EuiMarkdownFormat` has been removed in favor of using `EuiLink` and
`EuiText`.
2. Required `aria-label` attribute was added

# Screen 

<img width="1117" alt="image"
src="https://github.com/user-attachments/assets/66865703-92a5-4986-9b4e-573c5bd95fbc">

…stic#190421)

This PR aims to document custom metrics usage introduced in
elastic#189115.

## Summary

This PR
[seals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/seal)
`Object.prototype`, `String.prototype`, `Number.prototype`, and
`Function.prototype` on the Kibana server, which provides some measure
of protection against prototype pollution.

<details>
<summary>The Object.seal() static method seals an object.</summary>
**note** I currently have this marked as `backport:skip` to reduce the
risk of regressions in patch releases.

> The Object.seal() static method seals an object. Sealing an object
[prevents
extensions](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/preventExtensions)
and makes existing properties non-configurable. A sealed object has a
fixed set of properties: new properties cannot be added, existing
properties cannot be removed, their enumerability and configurability
cannot be changed, and its prototype cannot be re-assigned. Values of
existing properties can still be changed as long as they are writable.
seal() returns the same object that was passed in.
</details>

-----

## Help, this broke something!

Please let us know by opening an issue. If you need to get your
environment up and running quickly, you can disable these protections by
setting the `KBN_UNSAFE_DISABLE_PROTOTYPE_HARDENING` environment
variable to any truthy value.

This may be interfering with normal functionality if you encounter an
error similar to:
> Cannot add property foo, object is not extensible

Where `foo` is some arbitrary string.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

…ed integrations and required fields from the original rule (elastic#191065)

**Fixes: elastic#190628
**Related to:** elastic#173595,
elastic#173594

## Summary

As stated in the bug ticket, when duplicating a prebuilt rule, the
"Related Integrations" and "Required Fields" values should be inherited
from the original rule, as it was specified in the Acceptance Criteria
for elastic#173595 and
elastic#173594.

This PR:

- Removes the logic that resets these fields to empty arrays for
duplicated prebuilt rules - we needed this logic in the past because
these fields were not editable in the UI, but we don't need it anymore.
- Updates the corresponding unit tests.

## Screenshots

These screenshots were taken after introducing the fixes.

**Original prebuilt rule:**

<img width="1463" alt="Screenshot_2024-08-23_at_13_25_07"
src="https://github.com/user-attachments/assets/ad8673f5-aba3-40c8-ae91-bbd7d334b119">

**Duplicated prebuilt rule:**

<img width="1469" alt="Screenshot_2024-08-23_at_13_25_43"
src="https://github.com/user-attachments/assets/03761a2b-6f53-4bab-bf4c-a71c6860802b">

### Checklist

- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

…191087)

…ic#191233)

addresses elastic#190964

Third in the series of PRs to address general DQD tech debt

This one builds on previous 2 PRs 

elastic#190970
elastic#190978 

Gist of changes:

- split top level helpers into series of utils/* files
- each utils/ file is named after common behavior it export or works
with.
- cleanup dead code

elastic#190981)

## Summary

Fixes the memory usage chart visibility in the Nodes overview table 

### Checklist

- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

…91276)

Closes [elastic#190220](elastic#190220)

## Summary

This PR removes the `x` icon used to close the react query dev tools
which appeared in a non-development environment by restricting it to
appear only in development mode.

| before | after |
|-------|-------|
| <img width="1907" alt="image"
src="https://github.com/user-attachments/assets/28e68139-8f8b-4f13-aea3-76f9971b1ac0">
| <img width="1902" alt="image"
src="https://github.com/user-attachments/assets/7649f310-c531-4a01-aae4-c423c811cc48">
|

In a development environment, the icon stays and works as before: 

<img width="1890" alt="image"
src="https://github.com/user-attachments/assets/a7cd7479-f1cd-4504-812d-b3ade903dfb7">