This PR aims to resolve the issues with the GraphQL workspace, where requests from the collection tree and the ones open under tabs get dissociated following certain actions.

Dissociation due to request move and overwrite via spotlight Save as new request actions are beyond the scope.

Closes HFE-546 #4500.

What's changed

• The saveGraphqlRequestAs function exposed from the store premises, invoking the underlying dispatcher now returns the insertion index for the request being added.
• Updates the places of consumption of the above to leverage the insertion index and resolve issues with the pre-existing implementation where the request index came up as undefined resulting in dissociation with the tab.
• Updates signature for the OnAddRequest method in the CollectionGraphql component removing index (resolved as undefined) from the incoming data and leveraging the request index instead.
• Resolve type errors in the CollectionsGraphqlAddRequest component.
• Updates the GQL tab request save context schema enabling requirement for the requestIndex field existence as a follow up of feat: duplicate REST/GraphQL collections #4211.

Notes to reviewers

Please ensure to verify actions except for moves and overwrites via the Save as new request from the spotlight with requests from the collection tree and that the association is kept with the tabs in which they're open:

• Adding request under a root/child level collection.
• Saving the request open in the current tab under a collection. It should open the above request in a new tab.
• Editing a request.
• The above actions within the Save as modal.