Save cookie banner cookie across subdomains

[draganescu]

Fixes ##94071

Proposed Changes

• Add a domain to the cookie setting for the setTrackingPrefs util so that cookies are also applying to subdomains of that domain

Why are these changes being made?

• Because previously setTrackingPrefs omitted to set any domain and this resulted in only the current domain being set for the cookie.

Testing Instructions

1. Have a local calypso running under wpcalypso.wordpress.com
2. Checkout this PR
3. Edit your development config and set cookie_banner to true
4. Restart the calypso watcher
5. Have a sandboxed website
6. Visit wpcalypso.wordpress.com and delete the sensitive_pixel_options cookie via developer tools
7. Refresh
8. You should see the cookie banner
9. Accept all
10. Make sure your selected website is the sandboxed one (via hosting options)
11. Visit Settings > Media (this takes you out of Calypso)
12. You should not the cookie banner

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-129747

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-129747&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-129747&env=a8c-for-agencies

[draganescu]

I wonder if there should be some condition around the name of the domain and around setting it. There are calypso instances running in other domains, that's for sure.

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

App Entrypoints (~4 bytes added 📈 [gzipped])

name                 parsed_size           gzip_size
entry-subscriptions        +24 B  (+0.0%)       +4 B  (+0.0%)
entry-stepper              +24 B  (+0.0%)       +4 B  (+0.0%)
entry-main                 +24 B  (+0.0%)       +4 B  (+0.0%)
entry-login                +24 B  (+0.0%)       +4 B  (+0.0%)

Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• happy-blocks
• help-center
• notifications
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug fix/cookie-persistence on your sandbox.