feat: bulk resource selection and deletion with checkboxes

[SaviorVirus]

Description

Add multi-select checkboxes as the leftmost column in resource tables, enabling users to select multiple resources and delete them in bulk.

• Checkbox column with select-all/indeterminate header
• Bulk actions bar (count, delete, cancel) appears on selection
• Confirmation dialog with force delete option (bypasses grace period)
• Selection clears on kind switch; checked rows highlighted
• Parallel DELETE calls via useBulkDeleteResources mutation

Made-with: Cursor

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

How has this been tested?

• Tested locally against a remote cluster (EKS)
• Added/updated unit tests

Manually verified:

• Checkboxes appear as leftmost column on all resource kinds
• Select-all with indeterminate state works correctly
• Bulk actions bar shows/hides on selection
• Confirmation dialog lists selected resources with force delete option
• Parallel deletion completes and clears selection
• Kind switch resets selection

Checklist

• My code follows the project's coding standards
• I have performed a self-review of my code
• I have added comments where necessary
• My changes generate no new warnings
• Any dependent changes have been merged

Related issues

Fixes #291

[nadaverell]

I'm a bit worried this is a potentially risky flow, with insufficient safeguards, and also clutters the UI a bit when its actual usage is relatively rare.

I'd park this for a while to consider if it's actually worth doing. If we want to move forward with this, maybe add a small 3-dot menu on the top-right of the resource table, with an option to enter batch edit mode. That way power users can do this but it won't get in the way most of the time.

WDYT?

[SaviorVirus]

I'm a bit worried this is a potentially risky flow, with insufficient safeguards, and also clutters the UI a bit when its actual usage is relatively rare.

I'd park this for a while to consider if it's actually worth doing. If we want to move forward with this, maybe add a small 3-dot menu on the top-right of the resource table, with an option to enter batch edit mode. That way power users can do this but it won't get in the way most of the time.

WDYT?

i can't agree with you about overwhelmed ui, in my opinion it's ok. Also DELETE buttons are big, red and bright, i'm fully sure that everybody understand what does it mean.

What about side button to activate bulk menu, i thinking if implementing like this, almost nobody will knowing about this cos this would be counterintuitive.
But of course, you are product owner and this is yours final decision)

[nadaverell]

I'm a bit worried this is a potentially risky flow, with insufficient safeguards, and also clutters the UI a bit when its actual usage is relatively rare.
I'd park this for a while to consider if it's actually worth doing. If we want to move forward with this, maybe add a small 3-dot menu on the top-right of the resource table, with an option to enter batch edit mode. That way power users can do this but it won't get in the way most of the time.
WDYT?

i can't agree with you about overwhelmed ui, in my opinion it's ok. Also DELETE buttons are big, red and bright, i'm fully sure that everybody understand what does it mean.

What about side button to activate bulk menu, i thinking if implementing like this, almost nobody will knowing about this cos this would be counterintuitive. But of course, you are product owner and this is yours final decision)

Lets go with the side button to activate bulk menu. I think it's a reasonable middle ground.

[nadaverell]

Hey @SaviorVirus, friendly ping — still up for reworking this behind a side menu toggle?