Remove unityCrashId, as we don't use it anymore

[priettt]

• The backend isn't considering any case where NDK and JVM crashes have the same ID. It might even bring issues.
• We weren't setting the ID correctly. If installSignalHandlers gets posted to the main thread handler before we set the ID, we will always use different IDs.
• I tested crashes on an armeabi-v7a device, and we only get native crashes. The CrashDataSource handler never gets called.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Files

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.17%. Comparing base (9b81dfb) to head (74ff4b1).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1702      +/-   ##
==========================================
- Coverage   84.18%   84.17%   -0.01%     
==========================================
  Files         457      457              
  Lines       10684    10676       -8     
  Branches     1609     1606       -3     
==========================================
- Hits         8994     8987       -7     
  Misses        957      957              
+ Partials      733      732       -1     

Files with missing lines	Coverage Δ
...esdk/internal/capture/crash/CrashDataSourceImpl.kt	92.75% <100.00%> (-0.11%)	⬇️
...d/embracesdk/internal/injection/CrashModuleImpl.kt	100.00% <ø> (ø)
...bracesdk/internal/injection/CrashModuleSupplier.kt	100.00% <ø> (ø)
...droid/embracesdk/internal/ndk/EmbraceNdkService.kt	61.78% <100.00%> (-0.10%)	⬇️
...cesdk/internal/injection/ModuleInitBootstrapper.kt	88.52% <ø> (-0.04%)	⬇️

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[fractalwrench]

LGTM