[issue_tracker] Convert batch/normal mode toggle to tabs and implement permission control

[ay-bh]

Brief summary of changes

• Replaced the view toggle button with a tabbed interface using Tabs component
• Added permission check to show Batch Edit tab only for users with issue_tracker_developer permission
• Implemented data refresh when switching back to Browse Issues tab

Testing instructions

1. Login as a user without issue_tracker_developer permission - verify only "Browse Issues" tab is visible
2. Login as a user with issue_tracker_developer permission - verify both "Browse Issues" and "Batch Edit" tabs are visible
3. Make changes in Batch Edit mode, then switch back to Browse Issues - verify data refreshes automatically

Link(s) to related issue(s)

• Resolves [Issue tracker] make Batch mode visible only with developer permission  #9422, [issue_tracker] Batch mode: Button style should match LORIS #9423
• Part of [issue_tracker] batch mode - follow up #9418

Screenshot

[christinerogers]

lgtm but did not pull/test. thanks for taking care of this so quickly Ayush

@ay-bh confirm pls this doesn't create bottlenecks by loading all the data in both tabs at once, correct?

as a future enhancement we could consider hiding the Browse Issues tab for non-developers - the vertical space use doesn't make sense if it's the only tab option for end-users. @regisoc @racostas any strong feelings here?

[regisoc]

Thanks @ay-bh !

• PR rebase required.
• This looks clean. I like it.
• @christinerogers Agreed, tabs should be hidden for someone not having the right permission i.e. this could be completely hidden:

[racostas]

LGTM.

1. Tested with various uses/permissions looks good to me.
2. The tabs yet appear when the user have only the permission "not developer" but I think this is more cosmetic and should not stop us form merging this one
   

What do you think @regisoc , @christinerogers ?

[regisoc]

@racostas that is a cosmetic change, we can change it later.

[christinerogers]

@racostas that is a cosmetic change, we can change it later.

We're all agreed this is good to go, so I've just added this item under Second followups within #9418 PR description.

Ready for your review @driusan

addressed. @regisoc confirmed in the thread

[regisoc]

@christinerogers just to confirm.

[christinerogers]

3 approvals - over to @driusan for final review.
Ideally we could get this merged during this final GSOC submission week ending Nov. 8