RunList: use Custom filter

[VallariAg]

• Use custom filter to show filter inputs outside the table
• Add a button to expand/hide filter options
• Display sort button only on hover over the column title
• Disable column action buttons (all of it's functions can be performed with sort, filter, and show/hide column buttons on corner-right)
  Column Action button options:
  

Output:

[render]

Your Render PR Server URL is https://pulpito-ng-pr-84.onrender.com.

Follow its progress at https://dashboard.render.com/static/srv-cqvkcaqj1k6c73bs7nc0.

[netlify]

✅ Deploy Preview for pulpito ready!

Name	Link
🔨 Latest commit	f4de7d4
🔍 Latest deploy log	https://app.netlify.com/sites/pulpito/deploys/66bf462bca80f80008ec0cce
😎 Deploy Preview	https://deploy-preview-84--pulpito.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.

[zmc]

Good start! I think this will end up being a better UI than the default. Some early feedback:

• the new toggle button jumps around when the filters are shown/hidden
• the old toggle button (inside the table) is still present but nonfunctional
• the filter icon present in filtered columns is cut off; maybe it can be removed
• I think it would be good to group filters up logically, e.g.:
  • one group for "inputs" like branch, hash, suite - also scheduled date
  • a second group for "outputs" like status and ideally job counts (like runs with >N failed jobs)

What do you think?

[VallariAg]

Got it! All of these sound great, I'll start to work on these.

ideally job counts (like runs with >N failed jobs)

This would be harder to do right now because RunList has server side filtering. Even for "filter by username", I am working on adding username filter to paddles so we can support it in pulpito-ng. So I'll probably not include filter-by-job-counts in this PR but I can open a ticket for this because it sounds like a good idea.
I see the idea behind this grouping and it makes sense!

Another grouping that I was considering:

1. Build info: hash, branch
2. Run info: suite, machine_type, schedule_date
3. Results: status, job_counts