[9.2] Remove remaining logic and tests for subobjects:auto (#137428) (#…

…138640)

* Remove remaining logic and tests for subobjects:auto (#137428)

* Remove remaining logic and tests for subobjects:auto

* skip compat tests

* skip compat tests

(cherry picked from commit 8c110cb)

* Update muted-tests.yml

---------

Co-authored-by: Kostas Krikellas <131142368+kkrik-es@users.noreply.github.com>
Co-authored-by: Michail Romaios <84708293+mromaios@users.noreply.github.com>

Add validation to DER parser for seq len (#138683) (#138698)

Add validation to org.elasticsearch.common.ssl.DerParser for sequence
length that exceeds maximum signed int.

Add validation to DER parser for seq len (#138683) (#138697)

Add validation to org.elasticsearch.common.ssl.DerParser for sequence
length that exceeds maximum signed int.

Mute org.elasticsearch.upgrades.SearchStatesIT testCanMatch #137687

Update bundled JDK to 25.0.1 (#137640) (#137667)

(cherry picked from commit e486766)

Co-authored-by: Brian Seeders <brian.seeders@elastic.co>

[Transform] Handle missing geotile buckets (#137476) (#137696)

When the user configures missing buckets to be included in the
geotile_grid, Transforms should create the null bucket for the missing
bucket. This matches what a composite aggregation would return.

Fix #126591

Avoid counting snapshot failures twice in SLM (#136759) (#136849)

We came across a scenario where 3 snapshot failures were counted as 5
"invocations since last success", resulting in a premature yellow SLM
health indicator. The three snapshot failures completed at virtually the
same time. Our theory is that the listener of the first snapshot failure
already processed the other two snapshot failures (incrementing the
`invocationsSinceLastSuccess`), but the listeners of those other two
snapshots then incremented that field too. There we two warning logs
indicating that the snapshots weren't found in the registered set,
confirming our hypothesis.

We simply avoid incrementing `invocationsSinceLastSuccess` if the
listener failed with an exception and the snapshot isn't registered
anymore; assuming that another listener has already incremented the
field.

Update wolfi (versioned) (#136883)

This PR contains the following updates:

| Package | Type | Update | Change | |---|---|---|---| |
docker.elastic.co/wolfi/chainguard-base | final | digest | `e7cba12` ->
`b85d54c` | | docker.elastic.co/wolfi/chainguard-base | stage | digest |
`e7cba12` -> `b85d54c` | | docker.elastic.co/wolfi/chainguard-base-fips
| final | digest | `2229af4` -> `cbdc968` | |
docker.elastic.co/wolfi/chainguard-base-fips | stage | digest |
`2229af4` -> `cbdc968` |

---

### Configuration

📅 **Schedule**: Branch creation - "after 1pm on tuesday" (UTC),
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.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get
[config help](https://elastic.slack.com/archives/C07AMD4CNUR) if that's
undesired.

---

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

---

This PR has been generated by [Renovate
Bot](https://redirect.github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOS4xIiwibGFiZWxzIjpbIjpEZWxpdmVyeS9CdWlsZCIsIjpEZWxpdmVyeS9QYWNrYWdpbmciLCI+bm9uLWlzc3VlIiwiVGVhbTpEZWxpdmVyeSIsImF1dG8tbWVyZ2Utd2l0aG91dC1hcHByb3ZhbCJdfQ==-->

[Transform] Allow dynamic updates to frequency (#136757) (#136877)

Updates to a continuous transform's frequency should go into effect for
the next transform's checkpoint without needed to stop and restart the
transform.

Fix #133321

Limit default allocated processors for the test cluster (#133633) (#1…

…35910)

This is to ensure consistent test execution. It also supports clusters
 before 7.6 where the setting key was `processors` instead of `node.processors`