fix(config): add missing ORDER BY to Derby pagination queries

[daguimu]

Problem

Several pagination methods in ConfigInfoMapperByDerby use OFFSET/FETCH NEXT without ORDER BY, causing non-deterministic results across paginated requests. This is the Derby dialect equivalent of the MySQL bug reported in #14046.

Root Cause

Derby does not guarantee consistent row ordering without an explicit ORDER BY clause. When OFFSET/FETCH NEXT is used for pagination, different pages may return overlapping or missing records.

Fix

Added ORDER BY before OFFSET in all affected methods:

ConfigInfoMapperByDerby (8 methods):

• findConfigInfoByAppFetchRows — added ORDER BY id
• getTenantIdList — added ORDER BY tenant_id
• getGroupIdList — added ORDER BY group_id
• findChangeConfigFetchRows — added ORDER BY id
• findConfigInfoBaseLikeFetchRows — added ORDER BY id
• findConfigInfo4PageFetchRows — added ORDER BY id
• findConfigInfoBaseByGroupFetchRows — added ORDER BY id
• findConfigInfoLike4PageFetchRows — added orderBy("id") via WhereBuilder

Also added orderBy() method to WhereBuilder for fluent ORDER BY support.

Tests Added

All 8 corresponding test methods updated to verify the ORDER BY clause is present in the generated SQL.

Impact

Ensures deterministic pagination ordering for all Derby config queries. Consistent with existing methods in the same class that already use ORDER BY id.

[github-actions]

Thanks for your this PR. 🙏
Please check again for your PR changes whether contains any usage/api/configuration change such as Add new API , Add new configuration, Change default value of configuration.
If so, please add or update documents(markdown type) in docs/next/ for repository nacos-group/nacos-group.github.io

---

感谢您提交的PR。 🙏
请再次查看您的PR内容，确认是否包含任何使用方式/API/配置参数的变更，如：新增API、新增配置参数、修改默认配置等操作。
如果是，请确保在提交之前，在仓库nacos-group/nacos-group.github.io中的docs/next/目录下添加或更新文档（markdown格式）。