[Logs 8] Use a separate enum for SentryLogLevel

[adinauer]

#skip-changelog

📜 Description

Use a new enum SentryLogLevel for Logs.

💡 Motivation and Context

SentryLevel which is used by error events and breadcrumbs does not support level TRACE, therefore we need to use a separate enum for the log level of the Logs feature.

💚 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]

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

Generated by 🚫 dangerJS against 164f210

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	381.92 ms	410.92 ms	29.00 ms
Size	1.58 MiB	2.08 MiB	510.41 KiB

Previous results on branch: feat/separate-log-level-enum

Startup times

Revision	Plain	With Sentry	Diff
f5a3ee6	400.06 ms	414.27 ms	14.20 ms

App size

Revision	Plain	With Sentry	Diff
f5a3ee6	1.58 MiB	2.08 MiB	509.68 KiB

[lcian]

lgtm