* remove use of pdf to png conversion checker in comparison test
* remove use of pdf-to-img use in compare images service
* remove pdf-to-img dep from kibana
This PR re-activates and stabilizes the data frame analytics feature importance tests by reducing the job run time. It also scrolls the feature importance section into view during validation so in case of a failure the screenshot shows the relevant part of the screen.
* [Logs UI][Metrics UI] Remove deprecated config fields from APIs
* Fix typecheck
* Fix typecheck
* Fix typecheck
* Fix jest
* Fix functional test
* Remove extraneous timeField args
* Typecheck fix
* Consolidate log file changes to ResolvedLogSourceConfiguration
* Fix merge
* Revert additional logs files
* Revert inventory models
* Revert log_analysis api
* Fix timefield reference in process list
* Restore logs page files, fix typecheck on mock
* Fix functional test
* Restore inventory models index
* Fix typecheck on getFilteredMetrics
* Look CI if you don't tell me all the type errors at once I can't fix them all
* Maybe this is the last typecheck fix who knows
* Restore reading timestamp field from data view
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Unskipping test
* Commenting out fix and fixing another test
* Fixing functional test
* Fixing functional test agaaaiiinn
* Fixing the actual flake
* Splitting into two tests
* Maybe this time
* fix flaky test + adding functional test
* review + remove more jest flaky test
* fix type
* fix review/confusion
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary
This replaces the `console.log` we have with `ToolingLog` which is what the e2e tests want to use. Right now they're producing a lot of `console.log` debugging information and noise which we don't want. Instead we want to use the standard tool logging that e2e has for the FTR tests.
The two most important files with changes are:
* x-pack/test/detection_engine_api_integration/utils.ts
* x-pack/test/lists_api_integration/utils.ts
From there everything else is just a repeating pattern of:
```ts
const log = getService('log');
```
And then pushing the log into the utilities:
such as:
```ts
await deleteListsIndex(supertest, log);
```
For reviewers, if you want to, checkout this branch and just ensure I didn't miss a `console.log` statement within the e2e tests anywhere. Also double check I did the correct `log.debug` vs `log.error` or if you think I misinterpreted one, point it out. I use `log.debug` where I have retries and then I use `log.error` where I thought it would be most useful to call out a very probable or unexpected statement happening when the tests begin to go sideways or have issues.
### 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
* [APM] Improve service inventory perf
* Remove optimization for transaction groups api
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Fixes https://github.com/elastic/kibana/issues/115624
by increasing the timeout from 1 second to 5 seconds. Although jest is 5 seconds by default the `waitForNextUpdate` is by default 1 second. This adds a simple configuration to have it wait for 20 seconds before timing out which is what the flake is hinting at is a timeout that is beyond 1 second.
* [File data visualizer] Disabling create data view based on capabilities
* removing data view management card based on permissions
* fixing reset button and index data viz link
* use a feature flag to use the new pending actions logic
refs elastic/kibana/issues/116715
* switch off pending actions for endpoints when feature flag is disabled
review suggestions
* update/add tests to use FF
* correctly override the FF
`parseExperimentalConfigValue` method sets feature flag key values to `true` if passed as arg
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
