fix S3 image healthcheck

[bentsku]

Motivation

As reported and fixed in #10969, the S3 image health check had not been migrated following the refactoring/move into localstack-core (#10800). The fix is the same as #10894, and is now ported to the S3 image as well.

The original PR could not merge quickly due to the CLA, but in order to unblock the S3 image, we can merge this quicker.
Thanks again to @krishanbhasin-px for the fix.

Changes

• pick the health check from the regular localstack Dockerfile

[github-actions]

S3 Image Test Results (AMD64 / ARM64)

  2 files    2 suites   3m 5s ⏱️
404 tests 354 ✅  50 💤 0 ❌
808 runs  708 ✅ 100 💤 0 ❌

Results for commit 72101ef.

[alexrashed]

Thanks for this fix, and thanks to @krishanbhasin-px for pointing us to it. Since this issue might block a lot of other people, I agree that we should move somewhat fast on this.
It's a pity that we can't give the credit to you (by merging the original PR / getting your code in directly), but maybe you can get the approval and find something else to fix. 😛

[thrau]

✔️ Please add @krishanbhasin-px as co-author to the PR (Use the Co-Author syntax in the commit message)

[localstack-bot]

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 can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}