Add ability to disable data export

[fractalwrench]

Goal

Adds a disableDataExport function to our public API that prevents exporting data via OTel exporters or HTTP requests. This calls stop() which shuts down all executors internally, and deletes any persisted data/blocks OTel exporters from exporting more data.

The intention is that an app would call this function if a user opted out of tracking halfway through a session, and on the next launch they would conditionally initialize the Embrace SDK.

Testing

Added an integration test & ran manual tests in example app.

[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

Attention: Patch coverage is 95.65217% with 1 line in your changes missing coverage. Please review.

Project coverage is 85.44%. Comparing base (aba5549) to head (a62357c).
Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
.../java/io/embrace/android/embracesdk/EmbraceImpl.kt	88.88%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1757      +/-   ##
==========================================
+ Coverage   85.42%   85.44%   +0.01%     
==========================================
  Files         464      464              
  Lines       10818    10839      +21     
  Branches     1601     1604       +3     
==========================================
+ Hits         9241     9261      +20     
  Misses        860      860              
- Partials      717      718       +1     

Files with missing lines	Coverage Δ
...bracesdk/internal/logs/EmbraceLogRecordExporter.kt	71.42% <100.00%> (+7.79%)	⬆️
...ternal/opentelemetry/OpenTelemetryConfiguration.kt	100.00% <100.00%> (ø)
...d/embracesdk/internal/spans/EmbraceSpanExporter.kt	66.66% <100.00%> (+11.11%)	⬆️
...main/java/io/embrace/android/embracesdk/Embrace.kt	85.00% <100.00%> (+0.18%)	⬆️
.../java/io/embrace/android/embracesdk/EmbraceImpl.kt	76.82% <88.88%> (+0.70%)	⬆️

... and 2 files with indirect coverage changes

[bidetofevil]

Should we do the delete even if the SDK hasn't started yet?

[fractalwrench]

Yep, this sounds reasonable.

[bidetofevil]

Should we also disable session caching? Or perhaps just change the storage components to not actually persist any new payloads to disk? Trying to figure out if there are areas that might lead to writing any new data to disk.

[fractalwrench]

Calling stop() shuts down all the workers which effectively stops all future data persistence. I can add a comment that makes this clearer

[bidetofevil]

Ah nice!

[bidetofevil]

LGTM