fix: addWaiterTimeoutHandling

[haozhx23]

Issue #, if available:
the waiter_config for asynchronous inference in SageMaker SDK was unable to raise a PollingTimeoutError based on the configuration. The scenario that triggers this issue occurs when the time calculated by max_attempts * delay is less than the processing time of a single request. e.g. if the model takes 30s to process, and the waiter config setting is delay=2, max_attempts=5, the issue is triggered. The observed behavior is that the predict() method of an AsyncPredictor remains continuously blocked.

It's been found that in sagemaker-python-sdk, src/sagemaker/predictor_async.py, L253 _check_output_and_failure_paths()function, when one of the waiter exceeds max_attemps * delay, the WaiterError is catched but without any handling, so the while loop keeps checking one of the output file / failure file exists.

Description of changes:
L253 _check_output_and_failure_paths() function in src/sagemaker/predictor_async.py changed. Add a waiter_error event and checked in while condition.

Testing done:
Y

Merge Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.

General

• I have read the CONTRIBUTING doc
• I certify that the changes I am introducing will be backward compatible, and I have discussed concerns about this, if any, with the Python SDK team
• I used the commit message format described in CONTRIBUTING
• I have passed the region in to all S3 and STS clients that I've initialized as part of this change.
• I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added unit and/or integration tests as appropriate to ensure backward compatibility of the changes
• I have checked that my tests are not configured for a specific region or account (if appropriate)
• I have used unique_name_from_base to create resource names in integ tests (if appropriate)
• If adding any dependency in requirements.txt files, I have spell checked and ensured they exist in PyPi

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.