Incorrect "Cookie Set" status in a specific scenario

[gagan0123]

Describe the bug
In certain scenarios, the "Cookie Set" and "IBC Compliant" status as presented in the privacy sandbox is incorrect.

To Reproduce
Please refer to screencast for easier instructions

Steps to reproduce the behavior:

1. Launch the Google Chrome browser.
2. Navigate to settings and ensure third-party cookies are blocked.
3. Visit any website designed to set third-party cookies.
4. Access the Developer Tools and navigate to the Privacy Sandbox.
5. Verify the status of "Cookie Set" and "IBC Compliant" (they should be correct at this stage).
6. Keep the current tab active, and simultaneously open another tab to access the settings again. Here, change the setting to allow third-party cookies.
7. Return to the original tab (the one with the third-party cookies) and refresh the page.
8. Upon the first refresh, there will be a discrepancy as the browser sets the cookie but the Privacy Sandbox indicates that it hasn't.
9. Execute another refresh. At this point, the Privacy Sandbox should correctly reflect that the cookie has been set.
10. Open the settings in a separate tab again, and revert to blocking third-party cookies.
11. Go back to the original tab and refresh the page. The Privacy Sandbox may inaccurately display that the browser has set the cookie, even though it hasn't.
12. Remove the previously set cookie by navigating to Application > Cookies > domain.tld > third-party cookie in Developer Tools.
13. Despite the removal of the cookie, the Privacy Sandbox may still incorrectly indicate that the cookie is set.

Expected behavior
"Cookie Set" and "IBC Compliant" should show correct status as per user preferences and what the browser is actually doing.

Screencast

2023-07-19.19-03-05.Cookie.Set.and.IBC.Compliance.status.issue.with.Privacy.Sandbox.mp4

https://youtu.be/yMRGYYW70TM

Desktop (please complete the following information):

• OS: Pop!_OS 22.04 LTS
• Browser: Google Chrome
• Version: 114.0.5735.198 (Official Build) (64-bit)

[gagan0123]

The RFC for IBC compliance has already been expired and archived.

Ref: https://datatracker.ietf.org/doc/html/draft-west-cookie-incrementalism-01

Based on the above information, I suggest we simply remove the IBC compliance from the extension rather than fixing it.

[mohdsayed]

IBC compliant removed in #105

[gagan0123]

Updated description and removed mention of IBC Compliance

[gagan0123]

I've tested this out with the develop branch on commit 85e6898 and can confirm that the issue is no longer happening, so closing it.