[Stack 8.19.22-SNAPSHOT] [sentinel_one_cloud_funnel] Failing test daily: script test: routed_data_streams in sentinel_one_cloud_funnel.event

- Stack version: 8.19.22-SNAPSHOT
- 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.227s)
# Install an agent. (19.191s)
# Start the minio service with pre-loaded test data. (1.793s)
> docker_up -profile ${CONFIG_PROFILES}/${PROFILE} -network ${NETWORK_NAME} s1cf-minio
FAIL:
```

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

Start with routed_data_streams.txt and the `script test: routed_data_streams` entry point. Trace the `docker_up` call for the `s1cf-minio` service and inspect the Docker Compose profile used by `${CONFIG_PROFILES}/${PROFILE}`. Done means the service boots and the routed_data_streams test completes without the image pull failure.

Written by the indexing model from the issue text.