Add Retry to OTLP Exporter

[AaronRM]

Fixes #
Design discussion issue (if applicable) #

Changes

Please provide a brief description of the changes here.

Merge requirement checklist

• CONTRIBUTING guidelines followed
• Unit tests added/updated (if applicable)
• Appropriate CHANGELOG.md files updated for non-trivial, user-facing changes
• Changes in public API reviewed (if applicable)

[codecov]

Codecov Report

Attention: Patch coverage is 73.97260% with 38 lines in your changes missing coverage. Please review.

Project coverage is 79.3%. Comparing base (367e484) to head (98469f3).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
opentelemetry-otlp/src/exporter/tonic/logs.rs	0.0%	37 Missing ⚠️
opentelemetry-otlp/src/exporter/http/mod.rs	0.0%	1 Missing ⚠️

Additional details and impacted files

@@          Coverage Diff           @@
##            main   #2727    +/-   ##
======================================
  Coverage   79.3%   79.3%            
======================================
  Files        123     124     +1     
  Lines      22670   22800   +130     
======================================
+ Hits       17986   18093   +107     
- Misses      4684    4707    +23     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[lalitb]

tokio runtime won't be available here. Should we move this code under exporter/tonic, or if we want to keep it generic, one option could be to make the delay function configurable as an argument to retry_with_exponential_backoff - such that retry function can be callable from both async and blocking code.

[AaronRM]

The idea was the retry logic should be generic and used across all the OTLP exporters. Going to try that approach first and try to avoid the direct tokio dependency.

[cijothomas]

Suggested change

	otel_warn!(name: "OtlpRetry", message = format!("Retrying operation {:?} due to error: {:?}", operation_name, err));
	otel_debug!(name: "OtlpRetry", message = format!("Retrying operation {:?} due to error: {:?}", operation_name, err));