Allow user to provide custom filter in ListingTableUrl

**Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
Many object_stores are not as clean as expected. Eg: many have "hidden" files such as _SUCCESS or _temp/blahblah.
When using ListingTableUrl these files are not filtered and cause issues when inferring schema/options.

**Describe the solution you'd like**
ListingTableUrl has an optional glob but it would be more helpful if this was somewhat more generic, eg an optional Fn(&ObjectMeta) -> bool

**Describe alternatives you've considered**
We could implement the filtering at other layers in the application but they all seem to come with drawbacks/feeling awkward (eg: such filtering does not really belong in a wrapper around an object_store).

Inizia individuando ListingTableUrl e il relativo filtraggio glob opzionale esistente, quindi esamina come vengono utilizzati i metadati degli oggetti durante l’inferenza dello schema e delle opzioni. Il lavoro è completo quando un predicato opzionale sui metadati può escludere voci come i file nascosti prima dell’inferenza, con test che coprano il comportamento del filtraggio.

Scritto dal modello di indicizzazione a partire dal testo della issue.