Duo Developer failing with 401 unauthorized code
### Summary
After starting Duo developer it never properly gets off the ground but just ends with a 401 error.
Error:
```
<TraceableException wrapping Exception("Failed to update workflow with 'start' status: 401")> NoneType: None
```
### Steps to reproduce
Not found yet.
<!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. -->
### What is the current *bug* behavior?
Session never properly starts
<!-- Describe what actually happens. -->
### What is the expected *correct* behavior?
Session properly starts and executes.
<!-- Describe what you should see instead. -->
### Relevant logs and/or screenshots
[Langsmith Session](https://smith.langchain.com/o/477de7ad-583e-47b6-a1c4-c4a0300e7aca/projects/p/a4e68128-258a-41eb-b766-9414684ce34d?paginationModel=%7B%22pageIndex%22%3A0%2C%22pageSize%22%3A25%7D&timeModel=%7B%22duration%22%3A%227d%22%7D&peek=019c659e-8244-7a31-9550-b396e76e9e1c&peeked_trace=019c659e-8244-7a31-9550-b396e76e9e1c)
[GitLab Session](https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/-/automate/agent-sessions/2914177)
<!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code
as it's tough to read otherwise. -->
### Possible fixes
<!-- If you can, link to the line of code that might be responsible for the problem. -->
TBD
### Patch release information for backports
If the bug fix needs to be backported in a [patch release](https://handbook.gitlab.com/handbook/engineering/releases/patch-releases) to a version
under [the maintenance policy](https://docs.gitlab.com/policy/maintenance/), please follow the steps on the
[patch release runbook for GitLab engineers](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/patch/engineers.md).
Refer to the [internal "Release Information" dashboard](https://dashboards.gitlab.net/d/delivery-release_info/delivery3a-release-information?orgId=1)
for information about the next patch release, including the targeted versions, expected release date, and current status.
<!-- If you don't have /label privileges, follow up with an issue comment of `@gitlab-bot label ~"type::bug"` -->
issue