Inject RN bundleId with ASM

[priettt]

Goal

Similar to what we did with NDK symbols, inject the React BundleID with ASM. This allows us to remove resource injection altogether and access the bundle ID through the project instrumented config.

Testing

Modified integration test to verify injection

[github-actions]

Dependency Review

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

Scanned Files

None

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.63%. Comparing base (f396ec1) to head (e01ee51).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2199      +/-   ##
==========================================
- Coverage   85.63%   85.63%   -0.01%     
==========================================
  Files         465      465              
  Lines       10389    10381       -8     
  Branches     1522     1522              
==========================================
- Hits         8897     8890       -7     
- Misses        835      836       +1     
+ Partials      657      655       -2     

Files with missing lines	Coverage Δ
...racesdk/internal/buildinfo/BuildInfoServiceImpl.kt	100.00% <100.00%> (+16.66%)	⬆️
...id/embracesdk/internal/injection/CoreModuleImpl.kt	94.11% <100.00%> (-5.89%)	⬇️
...ternal/config/instrumented/schema/ProjectConfig.kt	83.33% <100.00%> (+3.33%)	⬆️

... and 3 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[bidetofevil]

Any reason why this is parallel to the config object rather than part of it?

It's not part of the Embrace config that we derive from the config file, but it certain seems parallel to things like buildId

[priettt]

it's mostly because we can't access it at the same time, but it'd be nice to aggregate the parameters in a class in the future, especially in createClassVisitor.

[bidetofevil]

LGTM. One question about why the bundleId doesn't live in the same object as the buildId