feat: use per-site permissions instead of managed content

[kamranayub]

I have seen whispers of setting the specific site URLs to allow instead, which I think would ultimately be a better approach. managed_default_content_settings is a heavy hammer that works but probably isn't the idiomatic way to handle this in the Chrome profile. Somewhere, a site's individual settings are stored and we may be able to poke at that.

I think we could check this fairly easily by setting it in the Cypress browser UI under Site Settings, then spelunking into the Cypress profile file to determine where it gets saved. That location is available in chrome://version I think.

[kamranayub]

I noticed in Edge by viewing the Preferences file that it stores things in

profile.default.content_settings.exceptions

in this format:

"notifications": {
          "http://localhost:51631,*": {
            "expiration": "0",
            "last_modified": "13281503591035274",
            "model": 0,
            "setting": 1
          },
}

So that may be an option?