fix(custom-fields): align #773 filter/sort with current master

[akira69]

Summary

This PR is intended as the small add-on / current-master alignment layer for upstream PR #773.

Conceptually:

• #773 is the main custom-field filter/sort feature
• #858 is the follow-up needed to keep that work aligned with current master

Important Branch Note

Although the intended scope here is the follow-up layer, this branch currently still contains the inherited #773 custom-field commits as its base.

So reviewers should read the scope like this:

• the underlying feature comes from #773
• the reason this branch still matters is the follow-up alignment/fix work on top of that feature set

If the #773 work is updated directly, this PR may no longer need to exist separately.

What #773 Covers

The primary custom-field feature set comes from #773, including:

• custom-field sort/filter behavior in list tables
• backend filter/sort support for custom-field types:
  • text
  • integer / float
  • boolean
  • choice (single + multi)
  • datetime
  • integer / float ranges
• range sorting using the low-end value
• integration coverage for custom-field filter/sort behavior

What #858 Adds

The follow-up work here is the current-master alignment layer:

• f70d801 fix(ts): align custom-field filter/sort typings with current master

In practice, this fixes the frontend/state-mapping edge so custom-field sort and filter state stays attached to the correct dynamic column when dataIndex is array-based.

Files directly relevant to that add-on:

• client/src/components/column.tsx
• client/src/utils/sorting.ts

Scope Boundary

This PR is only about custom/extra-field filter and sort behavior.

It does not include the broader searchable filter UX for standard columns. That work remains separate in #862.

So:

• #858 = custom-field / extra-field filter-sort behavior and alignment
• #862 = broader filter-dropdown UX improvements for normal columns

Validation

• Frontend build:
  • docker run --rm -v "$PWD:/app" -w /app/client -e VITE_APIURL=/api/v1 -e NPM_CONFIG_CACHE=/tmp/.npm -e XDG_CONFIG_HOME=/tmp/.config -e HOME=/tmp node:20 /bin/bash -lc "npm ci && npm run build"
• Integration coverage remains tied to the #773 custom-field stack:
  • tests_integration/tests/fields/test_filter_sort.py

Out of Scope

The following remain separate:

• table interactions / resizing (#861)
• searchable filter dropdown UX (#862)
• color / hex preview UI (#863)
• save / clear button state styling (#864)
• spool-count column extraction (#865)
• floating edit action layout (#866)
• column button wording (#867)
• show-page header touch-ups (#868)

Merge Coordination

1. #773 remains the primary feature reference for this area.
2. #858 should be treated as the follow-up alignment layer for that work, even though the branch still contains the inherited #773 commits.
3. If #773 is updated directly, the cleanest outcome may be to fold the f70d801 follow-up into that branch and close #858.
4. #862 and #865 do not duplicate this feature, but they touch adjacent API/database plumbing and may need a small rebase.

Shared touchpoints with #862 / #865:

• spoolman/api/v1/filament.py
• spoolman/database/filament.py

Additional shared touchpoints with #862:

• spoolman/api/v1/spool.py
• spoolman/database/spool.py
• client/src/components/column.tsx

Expected conflict scope is shared function signatures and adjacent logic, not duplicate feature behavior.

[akira69]

Closing this as superseded by #893 for the active PR 773 review-fix path.

The meaningful pieces from here are now covered there:

• backend review fixes: 9711495
• frontend table-state / TS cleanup: 3208f8d
• user-facing extra-fields settings copy update: 9abd208

Helper PR: #893
PR 773 review thread: #773