grpc-managed-channel sender ignores exporter RetryPolicy

Is your feature request related to a problem? Please describe.
We use opentelemetry-java in our platform and since https://github.com/open-telemetry/opentelemetry-java/pull/2995 all the services that start before the opentelemetry collector generate an ERROR log because the collector is not available yet:
https://github.com/open-telemetry/opentelemetry-java/blob/main/exporters/otlp/all/src/main/java/io/opentelemetry/exporter/otlp/internal/GrpcExporter.java#L100

Describe the solution you'd like

Describe alternatives you've considered

Additional context
We're using opentelemetry-java 1.63.0

从 exporters/otlp/all/src/main/java/io/opentelemetry/exporter/otlp/internal/GrpcExporter.java 的第 100 行附近开始，然后跟踪 grpc-managed-channel sender 如何处理 exporter 的 RetryPolicy。定义 collector 不可用时的预期行为，并验证启动时不再产生 ERROR 日志，同时 RetryPolicy 的行为仍然正确。