test(s3): simplify s3 configurations

[andrewazores]

Welcome to Cryostat! 👋

Before contributing, make sure you have:

• Read the contributing guidelines
• Linked a relevant issue which this PR resolves
• Linked any other relevant issues, PR's, or documentation, if any
• Resolved all conflicts, if any
• Rebased your branch PR on top of the latest upstream main branch
• Attached at least one of the following labels to the PR: [chore, ci, docs, feat, fix, test]
• Signed all commits using a GPG signature

To recreate commits with GPG signature git fetch upstream && git rebase --force --gpg-sign upstream/main

---

Related to cryostatio/cryostat-helm#247

Description of the change:

While working on the linked Helm issue and using the smoketest S3 configurations as references, I noticed that things could be cleaned up.

There is no need to explicitly set QUARKUS_S3_AWS_CREDENTIALS_TYPE=static, since the default value is default and uses a strategy of checking various provider sources, including the static provider. The static provider looks for a few options such as a home directory config file, as well as the already existing AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.

Also, cloudserver was missing a healthcheck definition which caused it to fail to start.

How to manually test:

1. Check out PR
2. ./smoketest.bash -s {provider}, where provider is one of seaweed, localstack, cloudserver, or minio (ie. any of the s3-*.yml compose files)
3. Wait for readiness, then open UI. Verify archive functionality is working as expected.

[andrewazores]

/build_test

[github-actions]

Workflow started at 5/16/2025, 11:05:57 AM. View Actions Run.

[github-actions]

No GraphQL schema changes detected.

[github-actions]

No OpenAPI schema changes detected.

[github-actions]

CI build and push: All tests pass ✅
https://github.com/cryostatio/cryostat/actions/runs/15071535929