[Improvement-18666] Support field sorting on workflow definition list

[chovy-3012]

Was this PR generated or assisted by AI?

NO

Purpose of the pull request

Close #18666
Add field sorting by name / createTime / updateTime to
the workflow definition list. Allowing users to sort by name, createTime, or updateTime by clicking the corresponding column header.

Brief change log

• Add sortField/sortOrder params to the workflow definition list query

Verify this pull request

This pull request is code cleanup without any test coverage.

(or)

This pull request is already covered by existing tests, such as (please describe tests).

./mvnw -pl dolphinscheduler-api -am test -Dtest='WorkflowDefinitionServiceTest,WorkflowDefinitionControllerTest' \
    -Djacoco.skip=true -Denforcer.skip=true -Dsurefire.failIfNoSpecifiedTests=false -q

(or)

This change added tests and can be verified as follows:

(or)

Pull Request Notice

Pull Request Notice

If your pull request contains incompatible change, you should also add it to docs/docs/en/guide/upgrade/incompatible.md

[boring-cyborg]

Thanks for opening this pull request! Please check out our contributing guidelines. (https://github.com/apache/dolphinscheduler/blob/dev/docs/docs/en/contribute/join/pull-request.md)

[SbloodyS]

Please follow the pull request notice.

[chovy-3012]

Please follow the pull request notice.

Thanks for the pointer — I've aligned this PR with the Pull Request Notice

[SbloodyS]

WorkflowDefinitionMapper.xml handles the field and direction fallbacks independently. Consequently, sortField=foo&sortOrder=asc produces update_time asc, id asc, whereas #18666 specifies update_time desc for unrecognized fields. Please apply the complete default ordering when sortField is invalid and cover this parameter combination.

[chovy-3012]

WorkflowDefinitionMapper.xml handles the field and direction fallbacks independently. Consequently, sortField=foo&sortOrder=asc produces update_time asc, id asc, whereas #18666 specifies update_time desc for unrecognized fields. Please apply the complete default ordering when sortField is invalid and cover this parameter combination.

Thanks. The field and direction were two independent blocks, so sortField=foo&sortOrder=asc fell back to update_time for the field but still honored asc for the direction, yielding update_time asc, id asc instead of the complete default.
Fixed by merging them into a single nested