Fix Multiple Cookie Issue: Properly Handle Multiple Set-Cookie Headers in ZitiUrlProtocol

[Dicky019]

This PR addresses an issue where multiple Set-Cookie headers in HTTP responses were not handled correctly by ZitiUrlProtocol. Previously, only one cookie would be processed, causing potential loss of additional cookies set by the server.

Key improvements:

• Correctly parses and collects all Set-Cookie headers from HTTP responses.
• Merges all cookie values into a single entry in the resulting dictionary, ensuring no cookies are missed.
• Resolves issues with authentication, session management, or any functionality relying on multiple cookies.

This fix improves compatibility with servers that set multiple cookies and ensures more reliable client behavior.
Please review and let me know if further changes are needed. Thank you!

[scareything]

Hi and thanks for the PR! It looks good to me. Can you please sign a contributor license agreement if you haven't already?

[Dicky019]

Hi and thanks for the PR! It looks good to me. Can you please sign a contributor license agreement if you haven't already?

Hi! Thanks a lot for checking it out 😊
Sure, I’ll go ahead and sign the CLA — will send it over shortly!

Let me know if there’s anything else I should do 🙌

[Dicky019]

Hi and thanks for the PR! It looks good to me. Can you please sign a contributor license agreement if you haven't already?

Hey, thanks for the reminder!
I’ve just sent the signed Individual Contributor License Agreement over to  cla@netfoundry.io

Let me know if there’s anything else you need!

[scareything]

Thanks for the cla. We have it. I just noticed that your commit on this PR is not signed, and we require signed commits. Could you please set up commit signing described here and amend your existing commit, then force-push?

[Dicky019]

Thanks for the cla. We have it. I just noticed that your commit on this PR is not signed, and we require signed commits. Could you please set up commit signing described here and amend your existing commit, then force-push?

Hi there, thanks for the heads‑up! I’ll configure commit signing as described, amend the existing commit with a GPG signature, and force‑push the branch shortly. Let me know if you need anything else!

[scareything]

Hi. I see that the commit is now signed, Thanks!

I'm guessing the changes in deps/ on your most recent push were inadvertent, and they are breaking the build. Could you remove your changes to those non-swift files? I'm guessing a git reset would be the easiest way.

Thanks.

[Dicky019]

Hi. I see that the commit is now signed, Thanks!

I'm guessing the changes in deps/ on your most recent push were inadvertent, and they are breaking the build. Could you remove your changes to those non-swift files? I'm guessing a git reset would be the easiest way.

Thanks.

Hi @scareything, sorry about that! I accidentally included changes to deps/ – I’ve reset those files and force‑pushed the branch. Build should be back to green now. Please let me know if you spot anything else. Thanks!