feat:(model-manager) add sorting capabilities for models

[skunkworxdark]

Summary

This PR introduces robust sorting capabilities to the Model Manager, allowing users to organize their installed models by several attributes in both ascending and descending order. This improves usability for users with large model libraries.

Related Issues / Discussions

#5885

Changes Made

• Backend (``invokeai/app/ & `tests/`):

  • Expanded the ModelRecordOrderBy enum to include Size, DateAdded, DateModified, and Path.
  • Added an order_by and direction query parameter to list_models and search_by_attr in model_records_base.py and model_manager.py.
  • Implemented SQL-based sorting in model_records_sql.py, notably using COLLATE NOCASE for string attributes (Name, Base) and json_extract to sort by file_size nested inside the config JSON.
  • Corrected the Default sort implementation to ensure the selected sort direction is correctly applied to all fallback columns (type, base, and name), rather than just the final column (format).
  • Added robust test coverage in test_model_records_sql.py to ensure proper ascending and descending functionality across different attributes.

• Frontend (``invokeai/frontend/web/):

  • State Management: Updated the modelManagerV2Slice to track orderBy and sortDirection globally.
  • API Integration: Passed the sorting arguments into the useGetModelConfigsQuery. Removed the client-side sortComparer from modelConfigsAdapter so the UI properly respects the server-provided order.
  • UI/UX: Added a new <ModelSortControl /> component to the ModelListNavigation panel.
  • i18n: Added full English localization strings for all sort options.

QA Instructions

1. Navigate to the Model Manager tab.
2. Ensure you have multiple models installed with varying bases, sizes, and names.
3. Locate the new Sort control in the top navigation bar of the Model Manager.
4. Try sorting by different parameters (Name, Base, Size, Date Added, etc.) and toggle between Ascending/Descending.
5. Change the sort mode back to Default and toggle the direction to verify that the list properly reverses the fallback groupings (Type, then Base, then Name).
6. Verify that the list updates correctly based on your selection and that the UI state persists across component unmounts.

Merge Plan

Standard merge. No Special instructions.

Checklist

• The PR has a short but descriptive title, suitable for a changelog
• Tests added / updated (if applicable)
• ❗Changes to a redux slice have a corresponding migration
• Documentation added / updated (if applicable)
• Updated What's New copy (if doing a release after this PR)

[joshistoast]

I'm still of the opinion personally that since the client has already fetched all the models, that it would be less intensive, faster and cleaner to sort on the client. But I digress.

The model search widget is starting too feel dense with the new direction toggle and sort by dropdown, they all have very different styles. Maybe we can get this all condensed into a unified filter dropdown each with submenus to select the desired filtering.

[skunkworxdark]

I'm still of the opinion personally that since the client has already fetched all the models, that it would be less intensive, faster and cleaner to sort on the client. But I digress.

The model search widget is starting too feel dense with the new direction toggle and sort by dropdown, they all have very different styles. Maybe we can get this all condensed into a unified filter dropdown each with submenus to select the desired filtering.

I'm not great with the frontend stuff, but I will take a quick look and see if I can do something without breaking everything. If not, maybe someone else, who is far more skilled than I, could do a UI PR for it later.

But I will take a stab at it first.

[skunkworxdark]

@joshistoast, what do you think of this?
If you think that is ok, I will commit it.

[joshistoast]

Yeah that looks much better @skunkworxdark. Small nitpick on the UI, maybe preserve the checkmark space on the left of non-selected item labels.

[ufuksarp]

Another important UX improvement would be for the drop-down menu to stay open (if not already), only closing when clicked outside or on the Filtering button.

[skunkworxdark]

@joshistoast indentation sorted. I think this is what you requested?

@ufuksarp, I am not exactly sure what you mean or what the point of your request would be. Can you expand on what you mean, or better still, provide an example of another menu in Invoke that behaves the way you are requesting?

[ufuksarp]

@skunkworxdark Ah, I thought the model selection was a multi-select with the checkmarks and all just seeing the images. My bad. Testing the PR now locally, all seems fine.

[skunkworxdark]

@skunkworxdark Ah, I thought the model selection was a multi-select with the checkmarks and all just seeing the images. My bad. Testing the PR now locally, all seems fine.

The model type filter selection hasn't been changed; it has only been rolled into a single dropdown menu along with the sort by and direction options to keep the header section clean.