fix: Handle 404 gracefully for public objects

[fenos]

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

Currently, we bubble up S3 error to the client when accessing a non-existing public object

What is the new behavior?

We will return 404

[coveralls]

Pull Request Test Coverage Report for Build 3489885068

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 7 of 7 (100.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.008%) to 86.774%

---

Totals
Change from base Build 3489221783:	-0.008%
Covered Lines:	4581
Relevant Lines:	5266

---

💛 - Coveralls

[github-actions]

🎉 This PR is included in version 0.24.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀