Draft: Fix: use standard cloud connector headers for workflow
What does this MR do and why?
This change refactors how authentication headers are handled in the DuoWorkflow service client. Instead of directly defining all headers in the metadata method, it now separates basic authentication headers from GitLab-specific headers, and uses a new CloudConnector.ai_headers method to provide the GitLab-specific information. This approach centralizes header management and adds a new header 'x-gitlab-duo-seat-count' that tracks the number of seats. The tests were updated to match this new structure, verifying that the CloudConnector.ai_headers method is called correctly and that all expected headers are included in requests.
References
How to set up and validate locally
- check out this branch and run a workflow pointed to your local GDK. ensure that it is still working as expected.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.