Fix ordering assets by integers, floats, and date fields

[duncanmcclean]

This pull request aims to fix an issue when ordering assets by integers, floats, dates, where the Eloquent Driver would consider the ints/floats/dates as strings, and order alphabetically, rather than numerically.

This PR takes a similar approach to #154 which fixed the same issue for entries, but I've refactored the logic to make it slightly tidier.

Before:

After:

---

Fixes #420.
Replaces #486.

[ryanmitchell]

This looks good, and is the right solution to fix the ordering issue. I think it should be merged to solve that immediate need.

However, thinking a bit further ahead to how we would solve issues like this one I wonder if we should be moving this logic to within function column() in the base eloquent query builder class.

take for example: https://github.com/statamic/cms/blob/d1e056b3be05d2df0bcbd92a818d11b08eff9e8c/src/Query/EloquentQueryBuilder.php#L185C32-L185C36

if this->column() returned the cast, we could do a ->whereRaw() based on it. Similarly for the other where clauses 🤔

[duncanmcclean]

However, thinking a bit further ahead to how we would solve issues like #416 I wonder if we should be moving this logic to within function column() in the base eloquent query builder class.

take for example: https://github.com/statamic/cms/blob/d1e056b3be05d2df0bcbd92a818d11b08eff9e8c/src/Query/EloquentQueryBuilder.php#L185C32-L185C36

if this->column() returned the cast, we could do a ->whereRaw() based on it. Similarly for the other where clauses 🤔

Interesting!

We could do the same sorta thing in ->where() (to fix that other issue), but it wouldn't fix the casting issue everywhere.

I don't know if we want to change what $this->column() returns because there are cases where you might want the column name, but not the casted stuff.

Happy to chat about it offline 🙂