[test] Surfacing deprecations with rich context from ES warning header

[rudolf]

Summary

Backport #120044 on 7.16 since I couldn't see any deprecation logs on main to verify that it works.

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)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• 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

[juliaElastic]

@rudolf is this intended to be merged? I would like to see if any deprecation stacktraces are coming from fleet plugin.
should I take this pr and run locally?
I checked the CI logs on this pr, but didn't see deprecation logs.

[spalger]

Returning true here isn't enough, it needs to get to the ToolingLogTextWriter.write() call below for true to actually mean "I wrote the message"

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: 8216ae3
• Interpreting CI Failures
• Storybooks Preview

Failed CI Steps

• Jest Tests #3
• Jest Integration Tests
• Checks

Test Failures

• [job] [logs] Jest Tests #3 / schema creates correct schema with defaults.
• [job] [logs] Jest Tests #3 / configureClient Client logging deprecation warnings from response headers does not log when no deprecation warning header is returned
• [job] [logs] Jest Tests #3 / configureClient Client logging deprecation warnings from response headers logs error when the client receives an Elasticsearch error response for a deprecated request originating from a user
• [job] [logs] Jest Tests #3 / configureClient Client logging deprecation warnings from response headers logs error when the client receives an Elasticsearch success response for a deprecated request originating from a user
• [job] [logs] Jest Tests #3 / configureClient Client logging deprecation warnings from response headers logs warning when the client receives an Elasticsearch error response for a deprecated request originating from kibana
• [job] [logs] Jest Tests #3 / configureClient Client logging deprecation warnings from response headers logs warning when the client receives an Elasticsearch success response for a deprecated request originating from kibana
• [job] [logs] Jest Tests #3 / CoreUsageDataService start getCoreUsageData elasticsearch.principal returns expected usage data for elastic.username "elastic"
• [job] [logs] Jest Tests #3 / correctly fills in default loggers config.
• [job] [logs] Jest Integration Tests / migration v2 logs a warning and completes the migration with unknown docs retained

Metrics [docs]

✅ unchanged

History

• 💔 Build #11091 failed 69f5778
• 💔 Build #10889 failed ed0e08b
• 💔 Build #10728 failed 5374ac7
• 💔 Build #10704 failed 2b6c7e00fc28a81579a1be323b651d61584c4d4b

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

[rudolf]

This work has been backported to 7.16 in #120882