SageMaker Bring Your Own Container on local mode - ProcessingOutput is not linked to local filesystem

**Describe the feature you'd like**
During the work with SageMaker BYOC on local mode (with Python SDK), we encountered the situation where the outputs of the container are staged into the SageMaker default artifact bucket. Then the SDK does not download those artifacts into the local file system.

**How would this feature be used? Please describe.**
We want that SDK will download the artifacts created automatically into the local file system.

**Describe alternatives you've considered**
We had to create a mechanism to download those files by ourselves:
In the following snippet of code, we used [https://github.com/aws-samples/amazon-sagemaker-local-mode/blob/main/scikit_learn_bring_your_own_container_local_processing/scikit_learn_bring_your_own_container_local_processing.py ](https://github.com/aws-samples/amazon-sagemaker-local-mode/blob/main/scikit_learn_bring_your_own_container_local_processing/scikit_learn_bring_your_own_container_local_processing.py) as a reference (also used the output_config dictionary)

Start with the Python SDK's local-mode ProcessingOutput handling and the output_config dictionary described in the issue. Read the linked scikit_learn_bring_your_own_container_local_processing.py example as a behavioral reference; done means artifacts staged in the default SageMaker bucket are automatically downloaded to the local filesystem.

Escrito por el modelo de indexación a partir del texto del issue.