Make user segment a top level property

[adinauer]

📜 Description

User segment is now a top level property.

💡 Motivation and Context

Closes #2240

💚 How did you test it?

📝 Checklist

• I reviewed the submitted code
• I added tests to verify the changes
• I updated the docs if needed
• No breaking changes

🔮 Next steps

[github-actions]

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

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

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

- Make user segment a top level property ([#2257](https://github.com/getsentry/sentry-java/pull/2257))

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 e635106

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	354.44 ms	362.06 ms	7.62 ms
Size	1.74 MiB	2.33 MiB	607.44 KiB

Baseline results on branch: main

Startup times

Revision	Plain	With Sentry	Diff
3d89dea	345.59 ms	364.06 ms	18.47 ms
1e4690d	354.69 ms	387.88 ms	33.19 ms
3d89dea	322.38 ms	350.82 ms	28.45 ms
2f079a1	296.91 ms	337.43 ms	40.51 ms

App size

Revision	Plain	With Sentry	Diff
3d89dea	1.74 MiB	2.33 MiB	604.92 KiB
1e4690d	1.74 MiB	2.33 MiB	604.92 KiB
3d89dea	1.74 MiB	2.33 MiB	604.92 KiB
2f079a1	1.74 MiB	2.33 MiB	605.56 KiB

Previous results on branch: feat/make-user-segment-top-level-property

Startup times

Revision	Plain	With Sentry	Diff
889d1d9	322.02 ms	341.21 ms	19.19 ms
c7dc7e4	357.37 ms	402.27 ms	44.90 ms

App size

Revision	Plain	With Sentry	Diff
889d1d9	1.74 MiB	2.33 MiB	605.65 KiB
c7dc7e4	1.74 MiB	2.33 MiB	605.55 KiB

[philipphofmann]

LGTM.

[marandaneto]

The class Request also has a other field which is not part of the spec either https://develop.sentry.dev/sdk/event-payloads/request/
I believe Request#data should be used instead as well, I'd confirm with the ingest team before doing this change tho, maybe raise a new issue.

[adinauer]

The class Request also has a other field which is not part of the spec either develop.sentry.dev/sdk/event-payloads/request
I believe Request#data should be used instead as well, I'd confirm with the ingest team before doing this change tho, maybe raise a new issue.

Created #2259 to track and do separately.