BUG: Don't copy DataFrame columns as metadata
See https://github.com/pandas-dev/pandas/pull/37186/files#r506978889.
Basically, we don't want to accidentally do `series.name =
dataframe.name` and try to set a column.

cc @jorisvandenbossche. This could conceivably affect geopandas, since geodataframe has different metadata than geoseries: https://github.com/geopandas/geopandas/blob/924cdf65c7c15b01749d1cdd036c5c291e87b0f4/geopandas/geodataframe.py#L83

But I don't think it'll actually break anything for you.
Also cc @arw2019 thanks @TomAugspurger  > This could conceivably affect geopandas, since geodataframe has different metadata than geoseries: https://github.com/geopandas/geopandas/blob/924cdf65c7c15b01749d1cdd036c5c291e87b0f4/geopandas/geodataframe.py#L83
>
> But I don't think it'll actually break anything for you.

Indeed, I also can't think of a situation where it would break anything (and our tests using pandas master didn't show up any failure). Whenever a metadata attribute existed on `self` but not on `other`, it would not be set to any value anyway