Unable to view pipelines due to failed security findings query

Checklist

• I'm using the latest version of the extension (see the latest version in the right column of this page)
  • Extension version: Put your extension version here
• I'm using the latest VS Code version (find the latest version here)
  • VS Code version: Put your VS Code version here
• I'm using a supported version of GitLab (see README for the supported version)
  • GitLab version: Put your GitLab version here, or say "happens on gitlab.com"

Summary

Hello,

Latest version of the GitLab Workflow extension doesn't show the pipelines "For current branch" box and instead shows: Error occurred, please try to refresh.

In the console it ends up with: [error]: The feature "Security Findings" is unsupported in GitLab version (15.11.x-ee). To use Security Findings, upgrade to GitLab version 16.1.0 or later.

I imagine this was not the intended.

Steps to reproduce

Use extension with your own gitlab < 16.1.0.

What is the current bug behavior?

For current branch box in vscode stays empty and shows Error occurred, please try to refresh.

What is the expected correct behavior?

Detect Security Findings isn't supported in that gitlab backend and just ignore that part of workflow extension so this box has something inside again like pipeline runs and jobs.

Relevant logs and/or screenshots

When I do refresh, in the extension logs I get:

2023-08-22T13:49:00:539 [error]: The feature "Security Findings" is unsupported in GitLab version (15.11.9-ee). To use Security Findings, upgrade to GitLab version 16.1.0 or later.
    Error: The feature "Security Findings" is unsupported in GitLab version (15.11.9-ee). To use Security Findings, upgrade to GitLab version 16.1.0 or later.
    	at /home/dev/.vscode-server/extensions/gitlab.gitlab-workflow-3.74.0/extension.js:447:1021
    	at Zn (/home/dev/.vscode-server/extensions/gitlab.gitlab-workflow-3.74.0/extension.js:218:366)
    	at ll.validateVersion (/home/dev/.vscode-server/extensions/gitlab.gitlab-workflow-3.74.0/extension.js:447:996)
    	at processTicksAndRejections (node:internal/process/task_queues:96:5)
    	at async qO (/home/dev/.vscode-server/extensions/gitlab.gitlab-workflow-3.74.0/extension.js:538:233)
    	at async Function.getState (/home/dev/.vscode-server/extensions/gitlab.gitlab-workflow-3.74.0/extension.js:538:2561)
    	at async e.refresh (/home/dev/.vscode-server/extensions/gitlab.gitlab-workflow-3.74.0/extension.js:538:1824)
    	at async gl.refreshSidebar (/home/dev/.vscode-server/extensions/gitlab.gitlab-workflow-3.74.0/extension.js:583:2140)
    	at async /home/dev/.vscode-server/extensions/gitlab.gitlab-workflow-3.74.0/extension.js:583:746
    	at async a.h (/vscode/vscode-server/bin/linux-x64/6c3e3dba23e8fadc360aed75ce363ba185c49794/out/vs/workbench/api/node/extensionHostProcess.js:103:77769)

Possible fixes

Using v3.73.0 / GitLab.gitlab-workflow@3.73.0