Remove old submissions table related code and removed fancybox

[sandeepsajan0]

Fixes #4224

• Removed old submissions all table code
• Removed old submission table batch actions
• Use htmx for invoice batch status update action

Test Steps

• All batch actions are working fine for new table.
• Invoice status batch update is working fine.

[frjo]

@sandeepsajan0 Added task to remove obsolete CSS, notices that when I created #4230.

[sandeepsajan0]

When I was looking at its failed test(user/test_middleware), I found an interesting issue that is somehow working fine in UI and passed the tests as well.
Actually, this url was added as a particular submission success page that has to be exempted from 2FA so we added it here in middleware but didn't add the submission id as it has to be dynamic. And it is working with middleware/UI because we are checking URLs by using 'startswith' but in the above test we are trying to access the same url without submission id that was unintentionally matching with path 'submissions/<str:status>' and then auth(redirect) and passing the test. As that path has been removed in this PR, test failed so for now I just added a submission and used that submission id to match success url.

But I think for the long-term instead of accessing the url we should only be testing the middleware code to check if it is going through or not? @frjo @theskumar

[frjo]

@sandeepsajan0 I have no merged #4188 in to main.

[frjo]

Did some minor lint fixes.

Notices this "+131 −1755", that is a lot of code lines we no longer need to maintain!

[frjo]

@wes-otf I believe @sandeepsajan0 fixed a bug regarding batch actions in the new submission all table as well in this PR.

[wes-otf]

seems like all worked pretty well! like @frjo said definitely nice to have that much to not maintain! Regarding the first test step, the only issue I saw with batch updating was I tried to do a batch action of dismissing these 6 and got a server error. @sandeepsajan0 / @frjo if that feels out of scope for this PR I can write up another issue

[frjo]

@wes-otf @sandeepsajan0 The submissions (only three show up on test today with this search) use different determination forms. This makes it impossible to dismiss them together in one batch run.

For status changes that require a determination (Accept, Dismiss and Invite for proposal) the batch status dropdown needs to check that the selected submissions use the same determination form. If easier we can check that they belong to the same round/lab.

The error message is not correct I believe, "Submissions expect different forms - please contact admin". The problem is that the forms are not the same from what I understand.