fix: process orderByParams before baseSortParams to preserve sort order for _score and custom fields

[zh-hanlabs]

What does this PR do?

Reorders the sort parameter processing in WrapperProcessor.setSort() so that orderByParams (set via orderBy(OrderByParam)) are appended to the DSL sort array before baseSortParams (set via orderByAsc/orderByDesc).

Why

Currently, setSort() processes baseSortParams first and orderByParams second. When a user calls wrapper.orderBy(scoreParam).orderByAsc(...).orderByDesc(...), the _score parameter goes into orderByParams while the field sorts go into baseSortParams. Since baseSortParams is processed first, _score always ends up at the end of the DSL sort array regardless of call order, producing incorrect sorting.

After this change, orderByParams are processed first, so the user-intended sort order is preserved in the generated DSL.

How to verify

1. Create a query with wrapper.orderBy(scoreParam).orderByAsc(status).orderByDesc(startDate)
2. Inspect the generated DSL — _score should now appear first in the sort array, followed by status and startDate

Closes #164