[11.x] Fix Cookie::queue to support domain-specific cookies

[Sajid-al-islam]

Description

This PR addresses the issue where setting two cookies using Cookie::queue(...) with the same name and path but different domains results in only one cookie being sent to the client, as the latter overwrites the prior. The issue is detailed in #53159.

Problem Description

The issue arises from how CookieJar currently stores queued cookies, only considering the cookie's name and path while ignoring the domain. The Symfony ResponseHeaderBag::setCookie() method, on the other hand, correctly differentiates cookies by domain in addition to name and path.

Solution

This PR updates CookieJar to take domains into account when queuing cookies. Specifically:

• The queue method now stores queued cookies using the cookie's name, path, and domain as keys, ensuring cookies with the same name and path but different domains do not overwrite each other.

Testing

• Added multiple test cases to verify that cookies with the same name but different domains or paths are queued and sent independently:
  1. Cookies with the same name and path but different domains are queued without overwriting each other.
  2. Cookies with the same name but different paths are handled correctly.
  3. Cookies with the same name, path, and domain result in the latter cookie overwriting the former (as expected).
  4. Verified behavior for secure, httpOnly, and other attributes.

[taylorotwell]

unqueue is part of the interface / contract so we can't change it on a patch release. You should just be able to attach the cookies to the response directly without using queue at all.