Keep around the current filter in query parameter for Discarding failed jobs

[TimeTravelerFromNow]

Solves #161 by adding the current parameters to the discard button
Alternative to turbo stream solution proposed in #270

Solution

Add the current parameters to the discard button path, with params: params.permit!

Continue submitting params in the Discard and Retry buttons so that the next request keeps filter

Steps to test

• Create some failed jobs of separate classes
• Apply the filter in the view
• Discard a job, check that it is deleted successfully and is removed from the view
• The filter for the job class remains selected in the next request

Thoughts on this approach

After discussing some possible drawbacks of turbo for Discarding jobs in the view:

• Incorrect state of discarded job if the server is down
• rendering the flash message
• Handling update the Failed job count display

I've come to the conclusion that for solving the issue of the filter persisting keep the params with the Discard button submission.

The hard refresh on redirect comes with the benefit of

• immediate feedback of server uptime
• Complete re-render ensures latest state is displayed
• No maintenance of turbo streams required

[rosa]

I changed this a bit to include only the job filters and not all params in the URL, and to also preserve the params in the redirects.

Nice work, and thank you!

[TimeTravelerFromNow]

@rosa good work, thanks for revisiting this one