Allow working within both global and workspace scopes

[yaugenka]

Currently one can either work in global scope (all data saved in one place) or project scope (bound to a workspace directory). In the former case you cannot save any data to a workspace and in the latter you cannot share data between projects (e.g. environments or template collections/requests) and cannot create temporary activities which should not be saved into the workspace.

To solve that I would suggest to allow working within both global and workspace scopes and resolve any conflicts with workspace having the highest prority.

1. When an activity, collection or environment is created the user should be asked to save it either in global or workspace scope. Would be nice to have a respective setting for the default choise.
2. Add options to Activities and Collections pannel menus to show/hide global scope entries.

[rangav]

@yaugenka the default storage location for all the data is global.

but if you like to save all the requests data in current workspace, you can do it by enabling the vscode setting Save To Workspace

so you can either save all data in global or current workspace, mixed is not possible and no plans to implement it.