Feature request: allowing for Retry to work with SageMaker steps

Currently, the `Retry` mechanism does not work with `TrainingStep `and `ProcessingStep` as the full job name must be specified to the step constructor so that if the step fails when the job has already been created, all retries will fail in submitting the job as the job name has already been used.
This happens for almost any error (including capacity errors) excluding throttling errors.

A possible solution might be to add an alternative parameter to specify a job name prefix, instead of a full name, and let SageMaker add some random suffix.

首先跟踪 TrainingStep 和 ProcessingStep 构造函数，以及 Retry 在失败后如何重新提交作业。检查 SageMaker 作业名称的处理方式，然后验证使用前缀和生成的后缀可以防止名称冲突，同时保留针对容量错误和其他非限流错误的重试。

由索引模型根据 Issue 内容生成。