Remove use of whitelist/blacklist in sdk api

[Ianfeather]

Summary

Could you update your API terminology for whitelistUrls and blacklistUrls to be more inclusive? This could be a breaking change or you could immediately accept additional properties alongside the existing ones and phase them out at the next scheduled release.

Motivation

The Code of Conduct says to use welcome and inclusive language and there's certainly more inclusive language that could be used for this part of the api. In addition, you're in the position of setting an example with the terminology that you choose to use. This post does a good job of detailing why the terms derive from prejudice: https://www.ncsc.gov.uk/blog-post/terminology-its-not-black-and-white

Additional Context

If allowList and denyList don't fit exactly, alternative API properties could be excludeUrls, includeUrls.

Thank you.

Prior conversation on other repositories:

• Replace use of whitelist with allowlist and blacklist with denylist rails/rails#33677
• Replace use of whitelist with allowlist and blacklist with denylist FullHuman/purgecss#428

[untitaker]

Moving this to sentry-javascript as those parameters exist purely in JS. inAppInclude is the regular name for a similar feature in other SDKs, so I think we should replace "whitelist" with "include" on consistency grounds as well.

[mitsuhiko]

This opens up the opportunity to fix the behavior of this parameter as well. It currently supports a substring match which we discussed before we might want to remove for an host portion only check.

[Ianfeather]

I really appreciate your response on this. Thank you.