Add s3a:// support

[dmoore247]

Is your feature request related to a problem? Please describe.
As stands, there are a number of cases where the startswith("s3://") test is applied. Unfortunately this will not work properly with s3a:// URIs to on-prem object stores.

Describe the solution you'd like
Support s3a://<host>/.... paths

Describe alternatives you've considered
A DBFS mount might be used with a classic, non-UC cluster, but would not work well with a managed UC table as a target.

Additional context
This would open up hybrid storage architectures, perhaps even cross cloud storage architectures.

[SARVESHYOGI]

Hi @dmoore247 👋
I’d like to work on this issue if it’s still available.

From what I see, the current logic checks for startswith("s3://"), which doesn’t support valid s3a:// URIs used by on-prem object stores. I can update the URI handling to support s3a:// while keeping existing behavior intact.

Please let me know if that sounds good or if there’s a preferred approach you’d like me to follow.