Add dedicated buffering module

Component(s)

No response

Is your feature request related to a problem? Please describe.

Currently, OpenTelemetry (Android) does not have a dedicated buffering module. This feature would be highly useful in scenarios where telemetry data cannot be immediately exported (e.g., due to network outages, app backgrounding, or battery optimization).

A buffering module (similar to what exists in opentelemetry-disk-buffering)

io.opentelemetry.contrib opentelemetry-disk-buffering 1.36.0-alpha runtime

would allow telemetry data to be persisted temporarily (e.g., on disk or in memory) and exported later once the system conditions allow it.

Motivation / Use Cases:

• Ensure telemetry data is not lost during intermittent connectivity.
• Improve reliability in mobile environments where background restrictions frequently interrupt telemetry export.
• Enable developers to configure buffer size, flush intervals, and persistence strategy (disk vs. memory).

Describe the solution you'd like

• Introduce a disk-buffering a option / module which can be used in opentelemetry-android.

• Reuse concepts and implementation patterns from existing buffering modules.

• Allow configurable storage backends (eg in-memory, file-based, SQLite).

• Related discussion: [open-telemetry/opentelemetry-android#1103](https://github.com/open-telemetry/opentelemetry-android/issues/1103)

Describe alternatives you've considered

No response

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

Start by reading the existing opentelemetry-disk-buffering module and the related opentelemetry-android issue #1103. Define the Android module's scope and storage approach before implementation. Done means telemetry can be buffered and exported later, with the requested configuration for buffer size, flush intervals, and storage strategy.