Bump sentry-dotnet SDK to add .NET 10 / PowerShell 7.6 support

[jamescrosswell]

`dependencies/Sentry.properties` currently pins `version = 5.16.1`. The 5.x line tops out at `net9.0` and has no `net10.0` build, so on PowerShell 7.6 (which runs on .NET 10) the module loads the `net9.0` Sentry assembly into a .NET 10 runtime, producing five `CS1701` warnings per import and — on some runtimes — turning those into a fatal `Add-Type` failure.

`net10.0` was added in sentry-dotnet 6.0; the latest stable is 6.5.0.

Scope

1. Bump `dependencies/Sentry.properties` to the latest stable `6.x`.
2. Add `Download -Dependency 'Sentry' -TFM 'net10.0'` to `dependencies/download.ps1` alongside the existing `net8.0` / `net9.0` / `net462` entries.
3. Add a `$PSVersionTable.PSVersion -ge '7.6' → 'net10.0'` branch to `GetTFM` in `modules/Sentry/private/Get-SentryAssembliesDirectory.ps1`, and update the version-mapping comment block.
4. Re-run `pwsh ./dependencies/download.ps1` to regenerate `modules/Sentry/lib/` and verify the samples still run on pwsh 7.4 / 7.5 / 7.6.
5. Audit for any 6.x breaking changes (5.x → 6.x is a major version bump).

Note

There is a PR that was generated automatically for this. Those auto bumps might work for minor bumps but a major bump like this is probably too complicated for it:

• chore(deps): update Dotnet SDK to v6.5.0 #109

[linear-code]

POWERSH-13