Automatically rename metadata columns that conflict with data schema columns

Today, if a datasource already has a column called `_metadata`, queries cannot access the file-source metadata column that normally carries that name. We can address this conflict with two changes to metadata column handling:

1. Automatically rename any metadata column whose name conflicts with a data schema column
2. Add a facility to reliably find metadata columns by their original/logical name, even if they were renamed.