Ignore certificate errors option not respected causing "self-signed certificate" error

Checklist

• I'm using the latest version of the extension (see the latest version in the right column of this page)
  • Extension version: 3.100.0
• I'm using the latest VS Code version (find the latest version here)
  • VS Code version: 1.85.2
• I'm using a supported version of GitLab (see README for the supported version)
  • GitLab version: 16.8.0-ee

Summary

Customer is using Squid proxy and a self-signed certificate, any Duo Suggestion or Duo Chat request returns error, no matter what config is being used for the IDE.

Using a temporary GitLab.com group with Duo Access and having them configure VSCode to point to it, allows the functionality to work

Steps to reproduce

Have a Squid proxy sit between Laptop and GitLab.

Have a self-signed certificate for your GitLab installation

Use VSCode, configure GitLab Workflow IDE with all relevant parameters (e.g. ignorecertificates, ... )

What is the current bug behavior?

Code Suggestions or Chat returns error (see log)

What is the expected correct behavior?

Duo Chat and Duo Code Suggestion works no matter the Self Managed instance architecture and configuration

Relevant logs and/or screenshots

Click to expand error logs

2024-01-26T12:50:05:908 [error]: {
   "userMessage": "Request failed: Can't add GitLab account for https://gitlab.local. Check your instance URL and network connection.",
   "errorMessage": "request to https://gitlab.local/api/v4/personal_access_tokens/self failed, reason: self signed certificate",
   "stack": [
    "FetchError: request to https://gitlab.local/api/v4/personal_access_tokens/self failed, reason: self signed certificate",
    "  at ClientRequest.<anonymous> (/home/local/jdoe/.vscode/extensions/node_modules/node-fetch/lib/index.js:1505:11)",
    "  at ClientRequest.emit (node:events:513:28)",
    "  at TLSSocket.socketErrorListener (node:_http_client:502:9)",
    "  at TLSSocket.emit (node:events:513:28)",
    "  at emitErrorNT (node:internal/streams/destroy:151:8)",
    "  at emitErrorCloseNT (node:internal/streams/destroy:116:3)",
    "  at processTicksAndRejections (node:internal/process/task_queues:82:21)"
   ]
  }

Possible fixes