### Describe the request

Currently, when sorting entries by a nullable field in Strapi, null values are placed at the end when sorting in ascending order and at the beginning when sorting in descending order. This behavior is consistent with common database sorting practices. However, there are use cases where it would be beneficial to have all null values sorted at the end, regardless of the sorting order (ascending or descending).

### Proposed solution

I propose adding a configuration option in Strapi to control the sorting behavior of null values. This would allow developers to specify whether null values should always be sorted last, providing greater flexibility to accommodate different use cases.

### Alternatives considered

An alternative could be to handle this at the application level, manually reordering the results after they are returned from Strapi. However, this would be less efficient and more complex than having the option built into Strapi itself.

---

This feature request is an extension of the discussion in Issue #12593. It was noted that Knex.js added a means to control if nulls are first or last, but this feature does not appear to be exposed in Strapi. Exposing this feature in Strapi would provide developers with more control over their data sorting behavior.