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

- Stack version: Same as in Pull Request builds
- Subscription: basic
- Package: amazon_security_lake
- Failing test: script test: routed_data_streams
- DataStream: event
- Owners:
- @elastic/security-service-integrations
- @elastic/sit-crest-contractors

Failure:
```
routed_data_streams.txt:26: 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 from the event data stream are routed to OCSF-category-specific
# data streams via routing rules.
#
# The test data in MinIO provides one event per OCSF category_uid value (1–6),
# derived from the pipeline test fixtures:
# - category_uid 1 → amazon_security_lake.system_activity (rerouted)
# - category_uid 2 → amazon_security_lake.findings (rerouted)
# - category_uid 3 → amazon_security_lake.iam (rerouted)
# - category_uid 4 → amazon_security_lake.network_activity (rerouted)
# - category_uid 5 → amazon_security_lake.discovery (rerouted)
# - category_uid 6 → amazon_security_lake.application_activity (rerouted)
#
#
```

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

Start with the `script test: routed_data_streams` entry and the referenced `routed_data_streams.txt` test. Inspect how its Docker Compose service is configured and why pulling `minio/minio` is denied. Done means the service boots successfully and the routed data streams test passes for the Amazon Security Lake event data stream.

Written by the indexing model from the issue text.