Use proper alias for table scope

[snipe]

Saw this pop up on the demo and it seems pretty straightforward. An error would be triggered if you try to sort on model name or number number, since the scope wasn't using the correct aliases.

We could probably clean up the requestable() method in the API controller as well, since we don't actually expose category, etc in that screen.

[shortcut-integration]

This pull request has been linked to Shortcut Story #23434: Illuminate\Database\QueryException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'models.id' in 'on clause' (SQL: select count(*) as aggregate from assets left join models as model_number_sort on assets.model_id = models.id where `.

[what-the-diff]

PR Summary

• Enhanced Asset Query Method
  The OrderModelNumber method in the Asset model, which is the blueprint for handling asset data in our system, has been updated. This change refines how we fetch specific information, particularly the model_number attribute. With this enhancement, our system can now fetch and order asset data more efficiently.