* Remove irrelevant warning

This commit removes an old warning which is no longer relevant to any supported
stack version. It is noisy and there is no action for the user to take.

* Add changelog entry for log removal

* 11.22.11 release prep

Update version in preparation for a release.

* Properly handle `413` Payload Too Large errors

Previously when Elasticsearch responds with a 413 (Payload Too Large) status,
the manticore adapter raises an error before the response can be processed
by the bulk_send error handling. This commit refactors the way
`BadErrorResponse` codes are handled. Previously we had logic in the manticore
adaptor which special cased raising errors on some codes. This commit refactors
such that the adaptor raises on any error status and the caller is now
responsible for special case handling the code.

* 12.0.2 release prep

* Use `error_code` instead of `code` when handling BadResponseCodeError

Previously a few bugs spotted in code review were being obfuscated by the
combinations of tests not running in CI and the incorrect method for retrieving
a code from a BadResponseCodeError. This commit updates the method names and
addresses the feedback from code review.

---------

Co-authored-by: João Duarte <jsvduarte@gmail.com>

…fixes) (#1219)

Adds two new headers to each bulk request:

* "X-Elastic-Event-Count": number of actions / documents in that bulk request
* "X-Elastic-Uncompressed-Request-Length": size in bytes of the request body before compression

X-Elastic-Uncompressed-Request-Length is equal to Content-Length when compression is disabled.

Backport fixes:

* Tolerate the elasticsearch-ruby v8 client in integration tests. (#1208)
* elasticsearch-ruby client got updated to v8 in LS core. This plugin uses it in integration tests. This change tolerates both elasticsearch-ruby v7 and v8 client versions.
* Fix the ILM spec issue where  method was removed, restored internally.

Co-authored-by: Mashhur <99575341+mashhurs@users.noreply.github.com>