fix: Issues with DO and existing registry

[qdzlug]

Describe the bug
If an existing container registry is present and I try to do a fresh deployment, it will fail in an extremely weird way. It'll say it can't authenticate and throw errors from our API, but it's able to interact with the API and it pulls the existing registry name out successfully. This is on an otherwise clean deployment on Ubuntu 22.10, fresh Droplet.

Note that the error messages indicate an auth failure, but this is not the issue (since we are still interacting with the API).

To Reproduce
Steps to reproduce the behavior:

1. Deploy to DO
2. Have an existing registry
3. BOOM (at registry step)

Expected behavior
Should add to the existing registry and move merrily along.

Your environment

Additional context
None

[qdzlug]

This is still happening in the most recent builds.