
Update `AutoConfigurationSorter` so that `getClassesRequestedAfter()` results are sorted to match the earlier name/order sorting. Prior to this commit the order of items added via `@AutoConfigureAfter` was in an undetermined order which could cause very subtle `@ConditionalOnBean` bugs. Thanks very much to Alexandre Baron for their help in diagnosing and reproducing this issue. Fixes gh-38904