CORS policy: Response to preflight request doesn't pass access co...

[harshvardhan60792]

Fixes #3379

Self-hosted S3-compatible bucket had no CORS policy after deployment, so browser uploads via presigned URLs failed preflight; s3-init now applies a permissive CORS policy right after creating the bucket, matching the workaround from the issue.

Testing: No JS/TS test suite applies to this docker-compose/shell change; validated narrowly by running only the s3 + s3-init services in isolation (not the full stack) and confirming via aws s3api get-bucket-cors and the exact OPTIONS preflight curl from the issue that access-control-allow-origin/methods/headers/max-age now come back, whereas the pre-fix s3-init left the bucket with no CORS config.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}