Support Bring Your Own Key (BYOK) functionality on headless oz-cli.
### Pre-submit Checks - [x] I have [searched Warp bugs](https://github.com/warpdotdev/warp/issues?q=is%3Aissue+label%3ABUG) and there are no duplicates - [x] I have [searched Warp known issues page](https://docs.warp.dev/help/known-issues) and my issue is not there - [x] I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). [Debugging ID instructions](https://docs.warp.dev/agent-platform/agent/ai-faqs#gathering-ai-debugging-id) - [ ] I have technical issue and have included the logs (optional, but helps expedite the bug fix). [Log instructions](https://docs.warp.dev/support-and-community/troubleshooting-and-support/sending-us-feedback#gathering-warp-logs) ### Describe the bug I am trying to use warp as port of our CI/CD, but I have to use my own keys (BYOK). On a machine where I also have WARP client installed, it's fine, but on a headless machine, there is no way to set them. Those keys are saved locally using the warp termin