feat: multiple tabs - [INS-4225]

[CurryYangxx]

Changes

• create a TabList and Tab Component, and import it in every type of file page.
• store tab data in localstorage, use InsomniaTabContext to manage state of the tabs
• create a useInsomniaTab hook
  • get tab type according to the location pathname
  • check if tab exist
  • pack tab data
  • add new tab
• sync tab data with db
• click "+" to add tab
• right click context menu: Close all & Close others
  • rename the origin IPC show-context-menu to show-nunjucks-context-menu
  • add a new IPC show-context-menu as the common context menu method
• support drag and drop to re-arrange tabs
• collection runner improvements: runner improvements (multiple tabs)-[INS-4779] #8244
• keep long connection for openning tabs: feat(tabs): keep connection for tabs-[INS-4778] #8266

related to #6108

[filfreire]

LGTM

Found issue where tabs disappear when pressing OPTION + TAB in the UI after a few times

some suggestions for this PR or other follow-up PRs:

• allow for pressing CTRL + TAB / CTRL + SHIFT + TAB to alternate between tabs
• perhaps also allow the same for pressing CTRL + 1 (1 to 9) to go to 1st -> 9th tab, 0 being last tab?
• allow middle-mouse click to close a tab
• capture COMMAND+W (and windows/linux equivalent) to close tabs

[kaynansc]

it would be nice capture COMMAND+W (and windows/linux equivalent) to close tabs

[CurryYangxx]

Update: (5e90726)
Because we can move a request or a folder to another collection. So, we need to update tab data after the move action.

• add patches field to database changeBuffer, so that we can know if user change the parentId
• request move
  • update tab by id (workspaceId, workspaceName, url)
  • revalidate workspace activeRequest
• folder move
  • batch update (workspaceId, workspaceName, url)
  • revalidate workspace activeRequest (if the activeRequest is in the folder, we need to clear it)

[filfreire]

@CurryYangxx, I took a pass at the branch again and tried after your commit and seems copying and moving seems to be working.

I noticed one other thing - for example if you have 2 tabs open for 2 requests, and maybe you are working on pre-request/after-response scripts, or docs, or headers.... etc. in both, the moment you switch tabs, you are not redirected to the "sub-tab" you were at when browsing the request.

So each time we switch between tabs we don't remember where inside the tab specifically the user was.

[jackkav]

improvement ideas for now or later:

analyse state choices against the choices in the rest app
localstorage, refs.
main map+useeffect?

db.onchange to trigger rerender
consider using the router loader instead of a surgical listener to get rerenders after state changes?

look for a way to remove the ref

look for a way to remove the event bus, figure out how to persist runner info on disk or local storage?

look for a way to remove the context provider, flatten useInsomniaTabContext into tablist and pass down function needed for tabs in react props

duplicate useInsomniaTabContext

enum to union

solve sync problems in runner upfront before this pr so this pr doesn't have to treat it as a special thing that needs lots of custom code