CR 121 - Sites added under Sites that can always use cookies block are not retained in an upgraded profile CR121

[GeetaSarvadnya]

Description

Found while testing #34702
Sites added under Sites that can always use cookies block are not retained in an upgraded profile CR121

Though CR 121 has a new UI design for the custom cookies settings block, the custom cookies sites added under the Sites that can always use cookies block are not retained upon upgrade to CR 121. However, chrome retains the custom cookies sites in an upgraded profile

Steps to Reproduce

1. Clean profile 1.62.x CR 120 build
2. Open brave://settings/cookies
3. Add few sites under Sites that can always use cookies block
4. Upgrade the profile to 1.64.x CR 121 build
5. Added cookies are not retained in the Allowed to use third-party cookies block

Actual result:

Sites added under Sites that can always use cookies block are not retained in an upgraded profile CR121

1.62.x	1.64.x

Expected result:

Sites added under Sites that can always use cookies block should be retained in an upgraded profile CR121 and sites should show under Allowed to use third-party cookies block

Reproduces how often:

Easy

Brave version (brave://version info)

Brave	1.64.2 Chromium: 121.0.6167.57 (Official Build) nightly (64-bit)
Revision	090e22f
OS	Windows 10 Version 22H2 (Build 19045.3930)

Version/Channel Information:

• Can you reproduce this issue with the current release? No
• Can you reproduce this issue with the beta channel? No
• Can you reproduce this issue with the nightly channel? Yes

Other Additional Information:

• Does the issue resolve itself when disabling Brave Shields? NA
• Does the issue resolve itself when disabling Brave Rewards? NA
• Is the issue reproducible on the latest version of Chrome? NA

Miscellaneous Information:

cc: @brave/qa-team @rebron @bridiver @ShivanKaul @mkarolin

[rebron]

cc: @goodov

[goodov]

This is Chromium change, apparently they expects users to click on Site settings icon in omnibox and configure Cookies from there from now on. Should we restore the good-old Cookies page or should we implement a separate page that can also control Shields and be clear about all cookies exceptions - that's the question for our product team.