Feat: native AOT debug info upload

[vaind]

closes #2692

This is mostly done in Sentry.targets - I've merged the two jobs (one uploading debug files, the second one uploading sources) because it was getting unwieldy when trying to handle both native AOT and managed symbols (and referenced sources) in both jobs.

I've also had to rework the PrepareCLI workflow a bit so that we get consistent integration test runs. Ppreviously, the integration test build would also upload symbols for the Sentry project itself, which is not what would happen when building actual user projects, because that project would have come from a nuget package.

TODO:

• force some source bundles to be uploaded for managed apps? it seems all sources are embedded with .net 8 SDK... How can we do it though? I'm open to suggestions
• test on Linux
• test on macOS (although the actual native integration will only come as a part of macOS native SDK integration #2625)

#skip-changelog (This is part of a bigger task to support Native AOT)

[github-actions]

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

Generated by 🚫 dangerJS against c9e7edf

[vaind]

FYI: This (and other similar cases below) is now handled by a condition in Sentry.targets property UseSentryCLI

[jamescrosswell]

I see we already have a CI_PUBLISHING_BUILD property... I take it this doesn't work because it's only ever set by by our github actions (and we want this to work even in the context of builds on local development machines)?

[vaind]

this is a transitive build target, so one that gets triggered during lib-consumer builds.

[jamescrosswell]

Aha... cunning. I had no idea we were doing that (or that it was even possible - never had a need before). Is that enabled simply by this?

sentry-dotnet/src/Sentry/Sentry.csproj

Lines 78 to 86 in d32f05b

	<!--
	Include Sentry's custom targets file in the nuget package.
	This file contains targets that are invoked during the end-user's build.
	The same file is included twice, so it ends up being used for both direct and transitive package references to Sentry.
	-->
	<ItemGroup>
	<None Include="buildTransitive\Sentry.targets" Pack="true" PackagePath="buildTransitive\Sentry.targets" />
	<None Include="buildTransitive\Sentry.targets" Pack="true" PackagePath="build\Sentry.targets" />
	</ItemGroup>

I think that's all we need to do right (reading the docs).

[vaind]

yes, that's it

[vaind]

and I've learned about this a couple of weeks ago myself, for the same reason :)

[bitsandfoxes]

Thanks for those!

[vaind]

yeah they're nice although at one point I've found myself just copying a piece of a code from one if branch to the other, forgetting to actually update the relevant condition 😅

[bitsandfoxes]