Pinging @elastic/es-search-aggs

test this please

I don't think the build failure is related to my commit. Failing test is an x-pack one:

10:56:05 > Task :x-pack:qa:rolling-upgrade:without-system-key:v6.4.0-SNAPSHOT#twoThirdsUpgradedTestRunner FAILED
10:56:05 Tests with failures:
10:56:05   - org.elasticsearch.upgrades.UpgradeClusterClientYamlTestSuiteIT.test {p0=mixed_cluster/30_ml_jobs_crud/Test get old cluster job}

@dbevacqua Yes, that is a ml test and is completely unrelated to the change. Can you merge master into your branch and push? This should trigger a new build.

@martijnvg done (though no new build so far...)

test this please

@dbevacqua Thanks! I'm going to add some more tests, so that there is more test coverage for multi level nested sorting. Right now that test coverage is poor. I think your fix is good, but having more tests should also increase confidence in this fix and whether multi level nested sorting is actual working.

test this please

@jpountz Would you like to take a look at this when you have time?

I am very sorry @dbevacqua, I tried to push to your branch to update this pr like @martijnvg did but I made something wrong and the pr got closed automatically. We discussed with @martijnvg about a simplification that should also fix #31783.
I opened a new pr with your commits and this additional change in #32204 which should add you as a co-author. Again sorry for the trouble.