docs(deployment): configuration page still says the S3 endpoint and region can be omitted if you use Minio #7929

Use case

#7927 / #7928 moved the development and CI stacks to Silo (pgsty/silo) and renamed MinIO to Silo in the documentation that names it as the object storage of the stack. A second git grep -i minio over main after the merge finds two prose mentions that were left behind, both in docs/docs/deployment/configuration.md (section "S3 bucket"):

• row minio.endpoint (line 212): "This parameter value can be omitted if you use Minio as an S3 Bucket Service."
• row minio.bucket-region (line 218): same sentence.

Everything else that still matches is the contract Silo keeps and stays as is: the minio.* / MINIO_* configuration keys and environment variables, the openaev-dev-minio / openaev-test-minio service names, the /minio/health/live healthcheck route, the MinIO Java SDK (io.minio, MinioClient, MinioDriver, MinioService) and its comments, the "Silo (MinIO fork)" wording introduced by #7928, and the historical 2.0.0 breaking-change note about the default bucket renaming.

Current workaround

None needed, documentation only.

Proposed solution

Say "if you use Silo as an S3 Bucket Service" in both rows, like OpenCTI-Platform/opencti#18244 does for the same page of the OpenCTI documentation.

Additional information

• Follow-up of chore(dev): replace the MinIO image by pgsty/silo in the development and CI stacks #7927 / chore(dev): replace the MinIO image by pgsty/silo in the development and CI stacks (#7927) #7928.
• Same second pass on the OpenCTI documentation: docs: pages still naming MinIO after the Silo switch - FIPS reference, map and configuration pages OpenCTI-Platform/opencti#18244 / docs(deployment): finish the MinIO to Silo rename after #18239 - FIPS, map and configuration pages (#18244) OpenCTI-Platform/opencti#18245.