More explicit size ordering

[brianjhanson]

Description

Explicitly orders by asset.size just in case users have a field with a handle of size. Reserved handles don't help us here because the columnMap used by orderBy uses all columns on the content table, so any entry type with a fieldHandle of size will cause issues.

Related issues

Fixes #12652

[brandonkelly]

This feels a little too lighthanded. It solves this one guy’s problem, but the same could still happen from any of the other asset-specific sortable attributes that don’t specify the table name in orderBy (or any other element type, for that matter).

So I just beefed up element queries’ automatic column name mapping for 4.4 via 74211f8. Going forward, all element extension table columns will be included automatically from joinElementTable() (unless the column name is already included in the mapping).