Add support for sameSite in cookie-related commands

[flotwig]

• Closes Allow sameSite in setCookie #2437
• Closes Yield sameSite attribute in getCookies #5070

User facing changelog

• Added support for setting sameSite via cy.setCookie().
• Added experimental support for adding sameSite to the objects yielded by cy.setCookie(), cy.getCookie(), and cy.getCookies(). Users can enable this by setting the experimentalGetCookiesSameSite config key to true. In Cypress 5, this will be the default.

Additional details

• getCookie/s support is behind an experimental flag: experimentalGetCookiesSameSite
• firefox and chrome have different API surfaces for samesite: https://bugzilla.mozilla.org/show_bug.cgi?id=1624668
  • firefox's default samesite will be no_restriction while chrome's will be unspecified
  • unknown if firefox will ever match chrome's behavior, but added driver tests to cover this if it does change
• support for sameSite in the proxy will come in another issue: cy.request unable to handle Same-Site: None cookie for cross origin requests #6757
  • this PR will also cover most of the changes for cy.request unable to handle Same-Site: None cookie for cross origin requests #6757 , but tests will need to be added

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• Has the original issue been tagged with a release in ZenHub?
• Has a PR for user-facing changes been opened in cypress-documentation? Document sameSite support for cookies commands cypress-documentation#2662
• Have API changes been updated in the type definitions?
• Have new configuration options been added to the cypress.schema.json?

[cypress-bot]

Thanks for the contribution! Below are some guidelines Cypress uses when doing PR reviews.

• Please write [WIP] in the title of your Pull Request if your PR is not ready for review - someone will review your PR as soon as the [WIP] is removed.
• Please familiarize yourself with the PR Review Checklist and feel free to make updates on your PR based on these guidelines.

PR Review Checklist

If any of the following requirements can't be met, leave a comment in the review selecting 'Request changes', otherwise 'Approve'.

User Experience

• The feature/bugfix is self-documenting from within the product.
• The change provides the end user with a way to fix their problem (no dead ends).

Functionality

• The code works and performs its intended function with the correct logic.
• Performance has been factored in (for example, the code cleans up after itself to not cause memory leaks).
• The code guards against edge cases and invalid input and has tests to cover it.

Maintainability

• The code is readable (too many nested 'if's are a bad sign).
• Names used for variables, methods, etc, clearly describe their function.
• The code is easy to understood and there are relevant comments explaining.
• New algorithms are documented in the code with link(s) to external docs (flowcharts, w3c, chrome, firefox).
• There are comments containing link(s) to the addressed issue (in tests and code).

Quality

• The change does not reimplement code.
• There's not a module from the ecosystem that should be used instead.
• There is no redundant or duplicate code.
• There are no irrelevant comments left in the code.
• Tests are testing the code’s intended functionality in the best way possible.

Internal

• The original issue has been tagged with a release in ZenHub.

[cypress]

---

Test summary

7030 • 0 • 98 • 0

---

Run details

Project	cypress
Status	Passed
Commit	e92ff79
Started	Mar 26, 2020 5:19 PM
Ended	Mar 26, 2020 5:25 PM
Duration	06:25 💡
OS	Linux Debian - 10.1
Browser	Multiple

View run in Cypress Dashboard ➡️

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard