Support multiple paths for ListingTableScanNode

[Ted-Jiang]

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Now ListingTableConfig

pub struct ListingTableConfig {
    /// Path on the `ObjectStore` for creating `ListingTable`.
    pub table_path: ListingTableUrl,
    /// Optional `SchemaRef` for the to be created `ListingTable`.
    pub file_schema: Option<SchemaRef>,
    /// Optional `ListingOptions` for the to be created `ListingTable`.
    pub options: Option<ListingOptions>,
}

Sometimes we need pass multi paths in ListingTableConfig like after file path prune we only need scan
/table/2020/01 and /table/2020/03 without /table/2020/02 (They should share the same schema and object store)
So we need pass

pub struct ListingTableConfig {
    /// Path on the `ObjectStore` for creating `ListingTable`.
    pub table_path: Vec<ListingTableUrl>,
    /// Optional `SchemaRef` for the to be created `ListingTable`.
    pub file_schema: Option<SchemaRef>,
    /// Optional `ListingOptions` for the to be created `ListingTable`.
    pub options: Option<ListingOptions>,
}

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.