fix: always prioritize games with release date when sorting by release date

[bhimbho]

No description provided.

[wescopeland]

Thanks!

[Jamiras]

We briefly discussed this behavior in #2706 (comment).

Jamiras:
As a player, I'd most likely look for either the oldest game on the list, or the newest, and wouldn't care at all about the ones without a date. As such, maybe it's better the way you had it.

and

wescopeland:
To be clear, I'm only seeing null dates appear at the bottom of the list if the sort is by earliest (ascending).
...
However, based on the findings reported in my previous comment, this is a behavior I'm in favor of.

Both #3116 and #2957 seem to want nulls to always be at the end, which this seems to address. I just want to make sure everyone is in favor of this change.

[wescopeland]

I've grown to think the change in this PR is most likely desirable for two reasons:

• It's one we keep hearing about on Discord and elsewhere.
• From my own day-to-day using the site as a player, seeing null dates first in the sort order is unexpected.

On the other hand, as an achievement developer, I do want to see the null dates first when I do this particular sort.

For the achievement developer persona, we should probably handle that use case in Filament.

[bhimbho]

Does this require any further delibration?

[wescopeland]

Hey @bhimbho 👋

We'll get around to merging this before we do our next release. Thanks!

[Jamiras]

On the other hand, as an achievement developer, I do want to see the null dates first when I do this particular sort.

For the achievement developer persona, we should probably handle that use case in Filament.

I don't think that's necessary. It might even be confusing for someone who is both a player and a developer. There's a page selector. If you're actively seeking the null values, you can just jump to the last page.