Add regression tests for sorting native queries with a derived table containing ORDER BY … LIMIT

[jewoodev]

The broken sort fragment reported in #2395 reproduces on the version it was filed against (2.3.9): QueryUtils.applySorting matched the derived table's inner ORDER BY and appended the primary sort after the WHERE clause without an order by keyword (… = :status, n.name asc), which becomes invalid SQL once pagination adds its LIMIT. It is no longer reproducible on main — both native query enhancers append the primary ORDER BY to the outer query while preserving the derived table's inner ordering.

This PR adds a regression test for each native enhancer: the regex-based DefaultQueryEnhancer, where the original breakage lived, and the JSqlParser-based JSqlParserQueryEnhancer, the default once JSqlParser is on the classpath. Each sits next to the existing shouldApplySorting coverage in its test class; both classes pass locally.

Closes #2395

---

• You have read the Spring Data contribution guidelines.
• You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.
• You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).