Project(s) selection parameter in CustomQueries

Problem to solve

If my current project does not track issues but I'm assigned to 2 issues in ProjectA and 2 issues in ProjectB, I would like to see and interact with all four of those issues in VSCode simultaneously, even if I'm working on ProjectWeb or ProjectAPI.

Proposal

We can use custom queries and passing in an array of relevant projects that we are interested getting issues from, e.g.:

  "gitlab.customQueries": [
    {
      "name": "All Issues assigned to you",
      "type": "issues",
      "scope": "assigned_to_me",
      "noItemText": "There is no issue assigned to you.",
      "state": "opened",
      "projects": ["current", "pathTo/projectA", "pathTo/ProjectB"]
    }
  ]

This would allow me to set this once in my settings.json and always see relevant issues assigned to me in the current project, ProjectA, and ProjectB simultaneously.

Further details

Our teams store issues in two central projects. All other projects have no issues in them. When we create MRs in an actual code repo project, we link them back to the issue(s) in the main projects. We would like to be able to see issues in VSCode from not only the current project that we are in. We typically use the parent Group Board/List view to access them in the UI.

Right now in VSCode, since there is no way to specify the project(s), there are no issues displaying for us since there are none in the current project.