Cody VSCE: Fix customHeaders never being passed through

[toolmantim]

This fixes cody.customHeaders so it's used instead of ignored. Reported by an Enterprise user who can no longer log into their instance, because the custom header isn't being passed.

After:

--> POST /.api/graphql?CurrentUser HTTP/1.1
--> Content-Type: application/json; charset=utf-8
--> Authorization: token a test token
--> Accept: */*
--> Content-Length: 89
--> User-Agent: node-fetch/1.0 (+https://github.com/bitinn/node-fetch)
--> Accept-Encoding: gzip,deflate
--> Connection: close
--> Host: localhost:3000

Before:

--> POST /.api/graphql?CurrentUser HTTP/1.1
--> x-test: test-test-test
--> Content-Type: application/json; charset=utf-8
--> Authorization: token a test token
--> Accept: */*
--> Content-Length: 89
--> User-Agent: node-fetch/1.0 (+https://github.com/bitinn/node-fetch)
--> Accept-Encoding: gzip,deflate
--> Connection: close
--> Host: localhost:3000

Test plan

• Set a custom header
• Run a local echo server (npx http-echo-server 3000)
• Sign in to server and observe headers
• Debug in VS Code and observe headers

[toolmantim]

This fixes customerHeaders always being truthy, which caused this line to never use this.config.customHeaders:

sourcegraph/client/cody/src/services/AuthProvider.ts

Line 197 in f5748b7

customHeaders: customHeaders || this.config.customHeaders,

[sourcegraph-bot]

📖 Storybook live preview