Build artifacts for failed builds

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have removed any sensitive information from my code snippets and submission.

### Amplify Hosting feature

E2E Cypress tests

### Is your feature request related to a problem? Please describe:

It looks like with Amplify 2, build artifacts can only be downloaded for successful builds, not failing builds. However, they are the most useful to us to troubleshoot things when our E2E tests are failing before deploying, therefore we need to be able to access them for failed builds too.

### Describe how you'd like this feature to work

Same as for successful builds but for failed builds too.


We can even see in the logs for failed builds that the artifacts are indeed uploaded to your S3 bucket `https://aws-amplify-prod-[region]-artifacts.s3.[region].amazonaws.com/[app_id]/[branch]/000000[build_number]/BUILD/artifacts.zip`, so it's not like they were not existing at all.


Start by reviewing the linked FAQ.md and the failed-build logs for the E2E Cypress flow, focusing on the S3 artifact path shown in the issue. Confirm how successful-build artifacts are exposed and define done as making the same artifacts downloadable after a failed build.

Written by the indexing model from the issue text.