fix: reset InteractiveTable pagination when filters applied [ET-183] [ET-121]

[EmilyBonar]

Ticket

ET-183
ET-121

Description

There were pagination problems occurring in the following situation:

1. user is on page N (N > 1) of an InteractiveTable
2. user applies table filter that makes the total number of pages < N, but which should still have entries
3. table appears empty

This ticket fixes the problem by resetting the table to the first page when filters are applied.

Test Plan

1. Find an InteractiveTable with > 10 elements where at least one column that can be filtered on has a mix of values
   • I suggest the Experiment Trials table on an errored multitrial experiment, those generally have a mix of completed and errored trials
2. Go to the last page
3. Filter the table by the aforementioned column
4. The table should reset to the first page

Checklist

• Changes have been manually QA'd
• User-facing API changes need the "User-facing API Change" label.
• Release notes should be added as a separate file under docs/release-notes/.
  See Release Note for details.
• Licenses should be included for new code which was copied and/or modified from any external code.

[netlify]

✅ Deploy Preview for determined-ui ready!

Name	Link
🔨 Latest commit	5da106e
🔍 Latest deploy log	https://app.netlify.com/sites/determined-ui/deploys/664f5d65235d9b00088227ee
😎 Deploy Preview	https://deploy-preview-9413--determined-ui.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

Attention: Patch coverage is 4.25532% with 45 lines in your changes are missing coverage. Please review.

Project coverage is 43.99%. Comparing base (860f6a8) to head (5da106e).
Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9413      +/-   ##
==========================================
- Coverage   51.22%   43.99%   -7.24%     
==========================================
  Files         747      423     -324     
  Lines      110720    70811   -39909     
  Branches     2778     2778              
==========================================
- Hits        56718    31152   -25566     
+ Misses      53827    39484   -14343     
  Partials      175      175              

Flag	Coverage Δ
harness	?
web	44.34% <4.25%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
webui/react/src/pages/Admin/UserManagement.tsx	83.39% <100.00%> (ø)
webui/react/src/pages/Templates/TemplatesList.tsx	0.00% <0.00%> (ø)
...t/src/pages/ExperimentDetails/ExperimentTrials.tsx	12.57% <0.00%> (+0.04%)	⬆️
webui/react/src/components/ModelRegistry.tsx	0.00% <0.00%> (ø)
.../pages/ExperimentDetails/ExperimentCheckpoints.tsx	13.52% <0.00%> (+0.03%)	⬆️
webui/react/src/pages/ExperimentList.tsx	0.00% <0.00%> (ø)
webui/react/src/components/TaskList.tsx	0.00% <0.00%> (ø)

... and 324 files with indirect coverage changes

[johnkim-det]

I think some of the places we're using InteractiveTable already include a tableOffset update in the handler passed to TableFilterDropdown's onFilter. Would making sure that all of those handlers include that update solve this issue? I think I'd prefer that approach if so.

[johnkim-det]

LGTM