[LogsDB] [Subscription basic] [sentinel_one_cloud_funnel] Failing test daily: script test: routed_data_streams in sentinel_one_cloud_funnel.event

- Stack version: maximum of either the version used in PR builds or 8.17.0 (GA version for LogsDB index mode)
- LogsDB: enabled
- Subscription: basic
- Package: sentinel_one_cloud_funnel
- Failing test: script test: routed_data_streams
- DataStream: event
- Owners:
- @elastic/security-service-integrations
- @elastic/sit-crest-contractors

Failure:
```
routed_data_streams.txt:19: setting up service: could not boot up service using Docker Compose: running Docker Compose up command failed: exit status 18: pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied: RUN routed_data_streams
# Verify that events are correctly routed from the event data stream to
# category-specific data streams via routing rules when rerouting is enabled.
#
# The test data in minio provides:
# - 2 dns events → sentinel_one_cloud_funnel.dns (rerouted)
# - 1 process event → sentinel_one_cloud_funnel.process (rerouted)
# - 1 file event → sentinel_one_cloud_funnel.event (retained, reroute_file not enabled) (0.000s)
# Connect to the running stack. (0.197s)
# Install an agent. (25.264s)
# Start the minio service with pre-loaded test data. (1.328s)
> docker_up -profile ${CONFIG_PROFILES}/${PROFILE} -network ${NETWORK_NAME} s1cf-minio
FAIL:
```

First build failed: https://buildkite.com/elastic/integrations/builds/49558

Start with routed_data_streams.txt for the sentinel_one_cloud_funnel package and inspect how the s1cf-minio service is started through Docker Compose. Reproduce the failure in the routed_data_streams script test, then verify that the MinIO service boots and the test completes with the expected routed data streams.

Written by the indexing model from the issue text.