Rename uses of term 'whitelist'

[jennifer-shehane]

• Closes cy.server whitelist behaves as blacklist #6642

User facing changelog

• The Cypress.Cookies.defaults() whitelist option has been renamed to preserve to more closely reflect its behavior.
• The cy.server() whitelist option has been renamed to ignore to more closely reflect its behavior.

Additional details

• This PR renames all instances of the the word whitelist in user-facing APIs, code, and tests.
• When renaming the keys, we decided to rename them based on the real intent/behavior of the keys, as opposed to maintaining a 1to1 matching change of what whitelist typically means. I think this will be more explicit upfront about what the keys function is rather than a generic whitelist or allow key.
• This PR does not change occurrences of the word for 3rd party integrations (Chrome and Firefox both have keys we need to send that include whitelist.

How has the user experience changed?

cy.server()

// Before
cy.server({ whitelist: () => {}})

// After
cy.server({ ignore: () => {}})

An error will now throw when defining whitelist function on cy.server().

// Before
Cypress.Cookies.default({ whitelist: 'session_id'})

// After
Cypress.Cookies.default({ preserve: 'session_id'})

An error will now throw when defining whitelist option on Cypress.Cookies.default().

This change makes it more inclusive by replacing terms that can be perceived as offensive to more self-explanatory names (blacklist/whitelist can reinforce the association of black as bad and white as good).

Examples of projects that already made the change:
Rails
Golang
Graphite Web
HTML

PR Tasks

• Have tests been added/updated?
• Been tagged in ZenHub release
• Has a PR for user-facing changes been opened in cypress-documentation? Rename uses of whitelist for renamed options. cypress-documentation#2928
• Has a PR for user-facing changes been opened in cypress-example-kitchensink? 5.0.0 Release cypress-example-kitchensink#430
• Have new configuration options been added to the cypress.schema.json?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[cypress]

---

Test summary

7824 • 0 • 107 • 0

---

Run details

Project	cypress
Status	Passed
Commit	314f3c5
Started	Jun 30, 2020 5:52 AM
Ended	Jun 30, 2020 5:59 AM
Duration	06:33 💡
OS	Linux Debian - 10.2
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

[jennifer-shehane]

@Saibamen This was an unanimous decision by our team to implement in this way and goes along with many other breaking changes as part of 5.0.0 release.

Please also keep in mind our code of conduct when commenting within our GitHub repo. Thank you.