Avoid NPEs from SDK in API like setTag, setData, setContext

[adinauer]

📜 Description

Using the SDK and having to guard against null is not a nice experience. Instead the SDK now tries to do the right thing when it receives null on APIs like setTag, setData, setContext, setExtra etc.

This means the SDK will:

• NoOp if the key is null (maybe returning null if a return type is specified)
• Unset the previous value if the value is set to null

💡 Motivation and Context

Fixes #4224

💚 How did you test it?

📝 Checklist

• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

[github-actions]

	Fails
🚫	Please consider adding a changelog entry for the next release.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

- Avoid NPEs from SDK in API like setTag, setData, setContext ([#4245](https://github.com/getsentry/sentry-java/pull/4245))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description.

Generated by 🚫 dangerJS against 6fdd4e7

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	389.13 ms	420.88 ms	31.75 ms
Size	1.58 MiB	2.21 MiB	642.23 KiB