ListingTable and FileScanConfig assume all files accessible via single ObjectStore instance

### Describe the bug

When attempting to read a table of files across multiple S3 buckets in a single query, the query will fail stating that files can't be found:
`Object Store error: Object at location test.parquet not found: Client error with status 404 Not Found: No Body`

This can be seen when the DataFrame is explained.

### To Reproduce

With an AWS account, create two buckets and place a test Parquet file in each.
Create an AmazonS3 ObjectStore instance for each file and register them via SessionContext::register_object_store with the S3 URIs.
Create a DataFusion query with SessionContext::read_parquet() that reads from both files.
Attempting to execute the query or show the explained query will show an error.

### Expected behavior

Query should execute and produce same result as if files were in same S3 bucket.

### Additional context

Amazon S3 ObjectStore instances are specific to the S3 bucket they read from. E.g. S3://bucket1/blah.parquet and S3://bucket2//blah2.parquet require two DIFFERENT ObjectStore instances.

The bug occurs in ListingTable which assumes all files in a table can be accessed via a single ObjectStore. This can be seen in numerous places such as the private list_files_for_scan function and the scan function. ListingTable creates the ObjectStore by just querying for the store associated with the first files in its list.

The same assumption is present in FileScanConfig

Start by tracing ListingTable, especially the private list_files_for_scan and scan functions, then inspect FileScanConfig where the single-ObjectStore assumption is also present. Reproduce the two-bucket S3 query described in the issue, and verify that execution and explanation succeed when files use different registered ObjectStore instances.

Written by the indexing model from the issue text.