Use Implementation-Version as raw version

[adinauer]

📜 Description

This mostly affects sentry-opentelemetry-agent as it used to have a complex version string in the Implementation-Version attribute of its MANIFEST.MF (e.g. sentry-8.5.0-otel-2.10.0). We now use the Sentry-Version-Name attribute for the complex version instead and keep Implementation-Version simple, e.g. 8.5.0.

💡 Motivation and Context

Implementation-Version is a common attribute and we should try to keep it simple. Also see https://docs.oracle.com/javase/tutorial/deployment/jar/packageman.html

💚 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 11cb785

[lcian]

Makes sense, so now Implementation-Version will be the release name right?
e.g. 8.0.0-rc1

[adinauer]

Makes sense, so now Implementation-Version will be the release name right?
e.g. 8.0.0-rc1

Yes exactly, since this is a commonly used attribute in MANIFEST.MF IMO it makes more sense to keep this as a simple value.

[lcian]

Makes sense, so now Implementation-Version will be the release name right?
e.g. 8.0.0-rc1

Yes exactly, since this is a commonly used attribute in MANIFEST.MF IMO it makes more sense to keep this as a simple value.

Yeah I agree!

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	451.00 ms	463.09 ms	12.09 ms
Size	1.58 MiB	2.22 MiB	655.16 KiB