Windows native support

[bruno-garcia]

Bringing sentry-native as a submodule which we can use to build native Linux and Windows.

Following install instructions from: https://docs.sentry.io/platforms/native/
Couldn't use the configuration listed there. Had to use Release.

Needed to add Directory.Build.props to src/sentry-native since CMake creates a .sln which ends up finding our Unity .prop files and fails to build due to not finding Unity installs. A possible solution for this that won't require changing sentry-native itself is to add the submodules to a directory (such as src/modules/sentry-native) and add the empty .prop and .targets in the modules directory.

Using crashpad means we need to distribute the game with the handler sitting next to it (or somehow provide the path to it when initializing the SDK). Alternatively we can use a backend such as the Android SDK and use the .NET layer to pick up those envelopes and send it to Sentry.

Also to figure out: We can't build and ship the package with building in a single CI agent now. We'll must build on Android + macOS and then assemble a package using bits taken from both builds.

Seems like assemblies such as Sentry.Unity.Android should be renamed to simply Sentry.Android since all they do is wrap our Android SDK without any Unity specific logic. Technically this code could be used by .NET Mobile in the future and made part of the core .NET SDK. Naming Sentry.Unity.Native for now but same here, should be Sentry.Native.

[vaind]

• TODO: from the native docs:

Warning
Calling sentry_close() before exiting the application is critical. It ensures that events can be sent to Sentry before execution stops. Otherwise, event data may be lost.

---

edit: moved to a new issue: #543

[bitsandfoxes]

Looks really good to me!

[bitsandfoxes]

Suggested change

	SentryNativeBridge.Init(options.Dsn!, options.Release!);
	SentryNativeBridge.Init(options.Dsn, options.Release);

Personally, I'd like to be a bit more defensive here and for example, pass the values down to the bridge and check/deal with them there.

[vaind]

• passing options down to Init()
• dsn is asserted to be non-null on android as well, so keeping as is
• making the release setting conditional

[bruno-garcia]

if ! is set here I assume the method doesn't accept nullable. So either we need to check for null before calling, or make the Init method take null and deal with it later.
If we can't have Init do its thing with null arguments, we should just check for those values here before we call and log in case we're not calling due to missing options.

[vaind]

Note: DSN is not null because options.Validate() must have returned true in SentryInitialization.cs for this to be called at all. I've added a comment.

[bruno-garcia]

Looking great!

[bruno-garcia]

if ! is set here I assume the method doesn't accept nullable. So either we need to check for null before calling, or make the Init method take null and deal with it later.
If we can't have Init do its thing with null arguments, we should just check for those values here before we call and log in case we're not calling due to missing options.

[bruno-garcia]

Thanks for doing this @vaind