Ensure specs on sorting of issues in API are deterministic on MySQL

What does this MR do?

Ensure a deterministic order of issues on the existing API issues specs

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

To avoid random failures as described on #22057 (closed)

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• CHANGELOG entry added
• [ ] Documentation created/updated
• [ ] API support added
• Tests
  • [ ] Added for this feature/bug
  • All builds are passing
• Conform by the merge request performance guides
• Conform by the style guides
• Branch has no merge conflicts with master (if you do - rebase it please)
• Squashed related commits together

What are the relevant issue numbers?

Closes #22057 (closed)