[cr133] CookieInclusionStatus instantiation changed

In production code, `ExclusionReason` cannot be passed through the
constructor anymore.

Chromium change:
https://chromium.googlesource.com/chromium/src/+/c2f7012ac0260de21f6773b7e93f6575713460f2

commit c2f7012ac0260de21f6773b7e93f6575713460f2
Author: Chris Fredrickson <cfredric@chromium.org>
Date:   Mon Dec 2 15:38:10 2024 +0000

    CookieInclusionStatus: Remove ctors which bypass invariants

    These ctors set the exclusion reason and warning directly,
    instead of using the dedicated setters which enforce
    invariants on the sets of exclusion reasons and warnings.
    It should not be possible to bypass the invariants, so we should
    remove these ctors.

    Change-Id: Ib60bf512e42a65fd76bd7701c7504878be8f580c

chromium_src/net/cookies/cookie_monster.cc

@@ -104,10 +104,12 @@ void CookieMonster::SetCanonicalCookieAsync(
   if (options.should_use_ephemeral_storage()) {
     if (!options.top_frame_origin()) {
       // Shouldn't happen, but don't do anything in this case.
-      MaybeRunCookieCallback(
-          std::move(callback),
-          CookieAccessResult(CookieInclusionStatus(
-              CookieInclusionStatus::EXCLUDE_UNKNOWN_ERROR)));
+      net::CookieInclusionStatus cookie_inclusion_status;
+      cookie_inclusion_status.AddExclusionReason(
+          net::CookieInclusionStatus::EXCLUDE_UNKNOWN_ERROR);
+
+      MaybeRunCookieCallback(std::move(callback),
+                             CookieAccessResult(cookie_inclusion_status));
       return;
     }
     ChromiumCookieMonster* ephemeral_monster =