Add a sort-order parameter to the deployment versions endpoint

[wandbjake]

Recent behavior on the deployment versions endpoint appears to return the oldest versions first, and we don't see a way to request newest-first ordering.

That means any client that wants to show the latest versions first now has to:

1. page through the full result set
2. fetch all versions client/server-side
3. sort locally by createdAt desc
4. optionally trim back down to a safe UI-sized list

It would be helpful if this endpoint supported an explicit sort-order parameter so clients could request the desired ordering directly.

Examples:

• sort=createdAt&direction=desc
• order=desc
• any equivalent API shape that makes newest-first deterministic

Why this would help:

• avoids extra pagination work for a very common "show latest versions" use case
• reduces payload size and client work
• makes UI behavior predictable
• avoids every integration having to reimplement the same workaround

If changing the default is undesirable for backwards-compatibility, a parameterized opt-in would still solve the problem cleanly.

[mleonidas]

This has been implemented #898