Use Sentry CLI after build to upload symbols

[mattjohnsonpint]

As part of #2074, this PR adds the following:

• Download and bundle the Sentry CLI with the Sentry nuget package
• Call the Sentry CLI to upload debug information files (symbols, etc.) after a successful build.

Currently requires setting the following environment variables manually before running the build.

• SENTRY_AUTH_TOKEN
• SENTRY_ORG
• SENTRY_PROJECT
• SENTRY_URL (if self-hosted)

See https://docs.sentry.io/product/cli/configuration/

[bruno-garcia]

It's odd to say, but that's some pretty msbuild code :)

[mattjohnsonpint]

Note, the verification snapshots previously had .../ in file paths because the buildTransitive\Sentry.props file was only imported to Sentry.Tests.csproj, so the project path assembly metadata attribute wasn't being added to the other test projects. Now that it's imported for all projects, it works correctly and strips the paths as intended.

[mattjohnsonpint]

Another verification failure was due to the way we were scrubbing attributes on the API verification tests. On CI, the path string was sometimes long enough that the attribute was printed on two lines and we only scrubbed one of them. Fixed.

[mattjohnsonpint]

Added the file hash verifications, and also went ahead and put the i686 (32-bit) versions in there too. Nuget size is 43MB, which is manageable.

[mattjohnsonpint]

Going to do some refactoring before completing this, as we'll want to separate the Sentry CLI setup from the symbol upload part, such that we can re-use it for other Sentry CLI tasks like creating releases, etc.

[bruno-garcia]

Generally seems good to go. Only a couple notes to clarify