Logging stability review: [minor] No `force_flush` on `LogRecordExporter`

[lmolkova]

Spec: Logs SDK § LogRecordExporter — operations: Export, ForceFlush, Shutdown.

• Recommended (SHOULD): ForceFlush lets a buffering exporter flush received records on demand.
• Current: LogRecordExporter ABC defines only export + shutdown. The force_flush methods in the logs export module belong to the processors (SimpleLogRecordProcessor, BatchLogRecordProcessor), not the exporter.
• Missing: LogRecordExporter.force_flush. Both SpanExporter and MetricExporter define it — logs is the only signal exporter without it.

Part of open-telemetry/community#1751

[lmolkova]

It seems it's already in progress - #5294

[DylanRussell]

What is force_flush supposed to do ? For the OTLP exporters it doesn't do anything:

opentelemetry-python/exporter/opentelemetry-exporter-otlp-proto-grpc/src/opentelemetry/exporter/otlp/proto/grpc/metric_exporter/__init__.py

Lines 291 to 293 in 50912be

	def force_flush(self, timeout_millis: float = 10_000) -> bool:
	"""Nothing is buffered in this exporter, so this method does nothing."""
	return True

There's already an export method which is supposed to export immediately..