fix(job_attachments)!: use correct profile for GetStorageProfileForQueue API

[gahyusuh]

What was the problem/requirement? (What/Why)

When submitting a job with a Storage Profile ID, the GetStorageProfileForQueue API was using the default AWS profile instead of the Deadline Cloud submitter's configured profile. If the two profiles pointed to different regions, the API couldn't find the storage profile resource, resulting in a job submission failure

What was the solution? (How)

Modified the code to use the correct boto3 session (using the Deadline Cloud submitter's profile) when calling the GetStorageProfileForQueue API. The API is no longer called from src/deadline/job_attachments/upload.py. Instead, the API is called from the below places:

1. src/deadline/client/api/_submit_job_bundle.py
2. src/deadline/client/ui/dialogs/submit_job_to_deadline_dialog.py
   and the prepare_paths_for_upload() function now receives storage_profile object itself instead of storage_profile_id.

What is the impact of this change?

Fixes the job submission issue when involving a Storage Profile in a different region than the default AWS profile.

How was this change tested?

1. I created AWS CLI's [default] profile and Deadline Cloud default profile, where each profile is pointing to different regions.
2. Before the change, job submission to a queue with a Storage Profile failed with a "storage profile does not exist" error.
3. After the change, job submission to the same queue succeeded, and the job could be created.
4. A new job was submitted to a Queue with a Storage Profile, and I executed a worker (CMF) to verify that asset sync and output downloads worked as expected.

Was this change documented?

No.

Is this a breaking change?

Yes, there are changes in the public interface (S3AssetManager's prepare_paths_for_upload()).

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[marofke]

Nit: since we're doing this in two places, we might want to make a function wrapper like what we've done in other places, like queue params https://github.com/aws-deadline/deadline-cloud/blob/mainline/src/deadline/client/api/_queue_parameters.py

Not blocking though, since we didn't hit the rule of 3 ;)

[gahyusuh]

Thank you for the advise. I have dded a function wrapper get_storage_profile_for_queue in client/api/_get_storage_profile_for_queue.py.

[chocecil]

I'm curious about the exception. When I ran this test, I received an "access denied" error. Was the related logic updated in this PR?

[gahyusuh]

Yes, I also saw the "access denied" error message. There were no updates related to this in this PR. I found it a bit strange that this integ test was failing... The error message that's currently showing up seems correct though - it's expected that PutObject would be denied if we try to upload a manifest file to a bucket that we don't have access to.