[Heap] Add a blacklist to prevent sending traits

[mfgea]

Add a blacklist to prevent sending the configured traits in the addUserProperties call

What does this PR do?

Adds a config entry in the Heap plugin. It is a list of fields that should be excluded from calls to the addUserProperties method.

Are there breaking changes in this PR?

No

Any background context you want to provide?

Some data compliance policies requires that no PII (Personally identifiable information) is sent to subprocessors. This change would allow that, combined with an id that's also non-identifiable.

Is there parity with the server-side/android/iOS integration components (if applicable)?

n/a

Does this require a new integration setting? If so, please explain how the new setting works

Yes. The setting is called blacklistedTraits, and it's an array of strings. The description might be: "List of traits (fields) that should be blacklisted from the identify calls to Heap".

Links to helpful docs and other external resources

https://help.heap.io/data-privacy/data-privacy-faqs/how-do-i-use-heap-to-comply-with-data-privacy-legislation/ https://en.wikipedia.org/wiki/Personal_data

[mfgea]

I think the Build process might be broken, as it failed at git cloning.