Add more tracing sections to startup

[bidetofevil]

Goal

Add more tracing sections to startup workflow to better profile SDK startup.

A misleading log line was also removed regarding loading native files

[bidetofevil]

• Hook up new components to log a startup trace #502
• Add activity listener that consumes lifecycle events and feeds AppStartupTraceEmitter #501
• Add component that adds traces to track app launches #500
• Don't create the OTel logger unless it's used #499
• Return more data from StartupService #468
• Add more tracing sections to startup #467 👈
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @bidetofevil and the rest of your teammates on Graphite

[codecov]

Codecov Report

Attention: Patch coverage is 91.55844% with 13 lines in your changes are missing coverage. Please review.

Project coverage is 79.45%. Comparing base (02a309f) to head (94c02db).
Report is 1 commits behind head on master.

❗ Current head 94c02db differs from pull request most recent head 949d501. Consider uploading reports for the commit 949d501 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #467      +/-   ##
==========================================
+ Coverage   79.41%   79.45%   +0.03%     
==========================================
  Files         376      373       -3     
  Lines       10204    10122      -82     
  Branches     1497     1474      -23     
==========================================
- Hits         8104     8042      -62     
+ Misses       1510     1500      -10     
+ Partials      590      580      -10     

Files	Coverage Δ
...in/java/io/embrace/android/embracesdk/Embrace.java	61.58% <100.00%> (ø)
...ava/io/embrace/android/embracesdk/EmbraceImpl.java	53.03% <100.00%> (ø)
...oid/embracesdk/injection/ModuleInitBootstrapper.kt	94.24% <100.00%> (-0.13%)	⬇️
...d/embracesdk/injection/DataCaptureServiceModule.kt	97.87% <96.29%> (+0.19%)	⬆️
...oid/embracesdk/injection/EssentialServiceModule.kt	95.65% <95.50%> (+0.30%)	⬆️
.../io/embrace/android/embracesdk/ndk/NativeModule.kt	78.04% <75.00%> (+1.73%)	⬆️

... and 18 files with indirect coverage changes

[fractalwrench]

LGTM

[fractalwrench]

Are these just being added as they're the biggest culprits? I was curious why these services are traced but others aren't

[bidetofevil]

Basically. I added a bunch of them and most aren't bad. I have another PR that needs more testing that starts to improve on some of these, but I'm not comfortable with getting that in so close to a release