fix(config): add ORDER BY to findConfigInfo4PageFetchRows for deterministic pagination

[daguimu]

Problem

The findConfigInfo4PageFetchRows method in ConfigInfoMapperByMySql uses LIMIT/OFFSET pagination in its inner subquery without an ORDER BY clause. Without explicit ordering, MySQL does not guarantee consistent row ordering across paginated queries, which can lead to duplicate or missing records when users paginate through config listing results.

Root Cause

The inner SQL query constructed in findConfigInfo4PageFetchRows() applies LIMIT directly without ORDER BY:

SELECT ... FROM config_info WHERE tenant_id=? ... LIMIT startRow,pageSize

This is the same class of bug as #14046 (which affected findConfigInfoLike4PageFetchRows), but in a different method that handles exact-match config queries rather than fuzzy queries.

Fix

• Added ORDER BY id before LIMIT in the inner query of findConfigInfo4PageFetchRows(), consistent with other paginated methods in the same class (e.g., findAllConfigKey, findAllConfigInfoBaseFetchRows, findChangeConfigFetchRows, listGroupKeyMd5ByPageFetchRows, findAllConfigInfoFetchRows).

Tests Added

Change Point	Test
Added ORDER BY id before LIMIT in inner query	testFindConfigInfo4PageFetchRows() — verifies the exact generated SQL contains ORDER BY id LIMIT
Same change point	testFindConfigInfo4PageFetchRowsWithDescAndTags() — verifies ORDER BY is present when all parameters (dataId, group, appName, content) are provided

Impact

This fix ensures deterministic pagination ordering for exact-match config queries on MySQL. Only the findConfigInfo4PageFetchRows method in the MySQL mapper is changed. No behavioral changes for other query methods or other database dialects.

[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格式）。