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.

Inizia da ModelTrainer.train() e segui la sua chiamata a _create_training_job_args(), dove l’issue mostra che viene assemblato il percorso S3. Esamina come viene gestita la lunghezza di base_job_name e individua i test correlati o i punti di ingresso per la costruzione dei percorsi. Il lavoro è completo quando ModelTrainer archivia i file dei job secondo il modello coerente richiesto, senza produrre percorsi malformati per i nomi lunghi.

Scritto dal modello di indicizzazione a partire dal testo della issue.