Fixed #14114 - correctly sort related fields for labels

[snipe]

Previously, if you selected multiple assets that were sorted in your list view, the labels would crash if you were sorting on something that wasn't directly on the assets table (category, model, location, status label, etc) with the error of

Illuminate\Database\QueryException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'status_label' in 'order clause' (SQL: select * from `assets` where `id` in (68, 66) and `assets`.`deleted_at` is null order by `status_label` desc)

since assets.status_label isn't a field, and we have to reach through assets.status_id -> status_labels.id to find out the name of the status label an asset has (and the same goes for company, category, etc). We already have those query scopes set up, since they're the same ones the API and listings pages use, so this implements them here as well.

This fixes RB-17764 and sc-24511, and is related to #14114.

[shortcut-integration]

This pull request has been linked to Shortcut Story #24511: PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'company' in 'order clause' in demo.snipeitapp.com/snipe-it/vendor/laravel/framework/src/Illuminate/Database/Connection.php:368.

[what-the-diff]

PR Summary

• Enhanced Sorting Functionality in Bulk Assets Management.
  • Enhanced the bulk assets controller with the ability to sort columns. This provides users with greater flexibility when viewing their asset data.
• Updated Hidden Input Values for Sort Order.
  • Amended the hidden values in the assets bulk actions code, which means the system now remembers the user's preferred sort order for more personalized and efficient data browsing.
• Optimized JavaScript code for user-friendly browsing.
  • The JavaScript code has been updated so it now organizes data based on the user's saved browsing preferences. This means a more seamless, user-centric browsing experience.

[marcusmoore]

One question but looks good 👍🏾