Feature support pipeline name in base_job_name at ModelTrainer

**Describe the feature you'd like**
i want to store the all files for jobs in a pattern like pipeline_name/job_name at this moment this is not possible for ModelTrainer class because train() function will call _create_training_job_args function which creates a s3 path like this:
s3://mybucket/my_pipeline_name/my_job_name/my-pipeline-name/my-job-name-20260318100943/input/sm_drivers/
or if the length of the base_job_name is longer then 63 the path could look like this:
s3://mybucket/my_pipeline_name/my_job_name/my-pipeline-name-extra-long-name/my-job-/input/sm_drivers/

**How would this feature be used? Please describe.**
This feature should be designed to help to store ModelTrainer files more consistently.
One suggestion for an S3 path would be {self.base_job_name}/input/20260318103152/sm_drivers/

**Additional context**
The Following Screenshot shows which code needs to be modified.

Commencez dans ModelTrainer.train() et suivez son appel à _create_training_job_args(), où l’issue montre que le chemin S3 est assemblé. Examinez la manière dont la longueur de base_job_name est gérée et identifiez les tests associés ou les points d’entrée de construction des chemins. Le travail est terminé lorsque ModelTrainer stocke les fichiers de job selon le modèle cohérent demandé, sans produire de chemins malformés pour les noms longs.

Rédigé par le modèle d'indexation à partir du texte de l'issue.