Tag pipelines and branch build pipelines are not being shown

Summary

(copied by @erran from #1246 (comment 1767692315))

1. No pipelines are displayed for tagged builds. So if .gitlab-ci.yml contains only: - tags no pipeline shows up in vs code. That is because tagged builds are not specific to branch, and we usually do not switch to tag. Switching branch to tag, pipeline displays correctly.
2. In older repositories, No builds are displayed for any branches except master if I switch to different branch like dev I cannot see pipelines for dev branch.

Proposed Solution

Displaying all pipelines with a filter for branch and tags just like how pipelines are displayed in GitLab.

Reproduction Steps

Reproducing is very easy, following steps will create pipelines only for tags, and you won't see them in VS code.

1. Create a simple npm package, just put a simple javascript and package.json
2. Use following packages.json
3. And use following yml
4. Replace ${PROJECT} and ${GITLAB_PACKAGES_KEY}
5. push changes
6. run npm version patch

package.json

{
  "name": "@your-project-name",
  "version": "1.1.1",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "node --enable-source-maps ./test.mjs",
    "postversion": "git push --follow-tags"
  }
}

.gitlab-ci.yml

stages:          # List of stages for jobs, and their order of execution
  - build

build-job:       # This job runs in the build stage, which runs first.
  stage: build
  tags:
    - build
  script:
    - echo "NPM Install"
    - npm install
    - echo "//${CI_SERVER_HOST}/api/v4/${PROJECT}/packages/npm/:_authToken=${GITLAB_PACKAGES_KEY}">.npmrc
    - npm publish --access=public --verbose
    
  only:
    - tags    

Original Description

Click to expand...

I just installed this extension and I did setup access token correctly from my self managed instance. Issues loads successfully but pipelines don't load, and in Gitlab Workflow output I see following error.

2024-02-07T17:30:25:587 [error]: Field 'duoChatAvailable' doesn't exist on type 'CurrentUser': {"response":{"errors":[{"message":"Field 'duoChatAvailable' doesn't exist on type 'CurrentUser'","locations":[{"line":4,"column":7}],"path":["query duoChatAvailable","currentUser","duoChatAvailable"],"extensions":{"code":"undefinedField","typeName":"CurrentUser","fieldName":"duoChatAvailable"}}],"status":200,"headers":{}},"request":{"query":"\n  query duoChatAvailable {\n    currentUser {\n      duoChatAvailable\n    }\n  }\n","variables":{}}}
    Error: Field 'duoChatAvailable' doesn't exist on type 'CurrentUser': {"response":{"errors":[{"message":"Field 'duoChatAvailable' doesn't exist on type 'CurrentUser'","locations":[{"line":4,"column":7}],"path":["query duoChatAvailable","currentUser","duoChatAvailable"],"extensions":{"code":"undefinedField","typeName":"CurrentUser","fieldName":"duoChatAvailable"}}],"status":200,"headers":{}},"request":{"query":"\n  query duoChatAvailable {\n    currentUser {\n      duoChatAvailable\n    }\n  }\n","variables":{}}}
    	at AD (c:\Users\user1\.vscode\extensions\gitlab.gitlab-workflow-3.101.1\extension.js:292:8246)
    	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    	at async xie (c:\Users\user1\.vscode\extensions\gitlab.gitlab-workflow-3.101.1\extension.js:765:153)
    	at async Uh.getGitLabPlatform (c:\Users\user1\.vscode\extensions\gitlab.gitlab-workflow-3.101.1\extension.js:765:399)
    	at async Fie (c:\Users\user1\.vscode\extensions\gitlab.gitlab-workflow-3.101.1\extension.js:765:706)
    	at async qie (c:\Users\user1\.vscode\extensions\gitlab.gitlab-workflow-3.101.1\extension.js:765:838)
    	at async c:\Users\user1\.vscode\extensions\gitlab.gitlab-workflow-3.101.1\extension.js:765:941

I don't have duo chat configured on my self managed instance.