We've noticed that when converting an Arrow Table to pandas using `.to_pandas()` integer columns with null values get converted to float instead of using pandas nullable types.
If the column was created with pandas first it is correctly preserved (I guess it's using stored metadata for this).
I've attached a screenshot showing this behavior.
As currently there is support for nullable types in pandas, just as in Arrow, it would be great to use these types when dealing with columns with null values.
If you are reticent to change this behavior, a param would be nice too (e.g. `to_pandas(use_nullable_types: True)`).