[FLINK-39107][tests] Run otel container from a prebuilt image

[Efrat19]

What is the purpose of the change

We are hitting docker build issues when multiple tests are building otel from a dockerfile in parallel. While it could be addressed by a resource lock, we realized we could actually use the prebuilt image with a mounted output directory instead of building from dockerfile. It is also the recommended approach by docker to use volumes for writable locations, to avoid copy-on-write bottlenecks

Brief change log

• Use a prebuilt otel image with a mounted output directory instead of building from dockerfile.

Verifying this change

This change is already covered by existing tests, such as:

• org.apache.flink.metrics.otel.OpenTelemetryMetricReporterITCase
• org.apache.flink.traces.otel.OpenTelemetryTraceReporterITCase

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

[Efrat19]

@flinkbot run azure

[flinkbot]

CI report:

• b69c4db Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[MartijnVisser]

LGTM, given that CI passes of course. Thanks for addressing it!

[Efrat19]

@flinkbot run azure

[Efrat19]

@flinkbot run azure