Reset table offset when DagFiltering changes

[pierrejeambrun]

Remove the offset from the search param when we modify DagFilters.

Otherwise this would wrongly display "no result found" on the front-end but just because we are requesting an offset that does not exist.

How to reproduce:

• Browse the dag list, going for instance to page 2 or 3.
• Modify one of the filters of the DagsFilters component, see that 'no results' will appear (suposing there isn't 2 or 3 pages of result for that filtered query), but actually there are some results.

Before

(clicking on "failed" when on page 3 will not reset the offset to 0, API will resturn no result for page 3 + failed state ending up in no result displayed in the UI).

After

(clicking on "failed" when on page 3 will reset the offset to 0 and display the proper result)

[github-actions]

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker 5de7cda v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

[pierrejeambrun]

Manual backport pick #51795