WIP: Removing default scope in Sortable

What does this MR do?

It removes the default scope from Sortable.

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

It may be tricky to find which controllers/APIs depend on this at the moment.

Why was this MR needed?

#23075 (closed) illustrates the perils of adding a default scope. For example, the ORDER BY can cause a significant performance issue by causing the SQL optimizer to use a non-ideal index.

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 it does - rebase it please)
• Squashed related commits together

What are the relevant issue numbers?

Closes #23079 (closed)