TST: fix parquet test_pandas_timestamp_overflow_pyarrow test

[jorisvandenbossche]

This test started failing on arrow master (noticed thanks to our nightly builds testing dask). The reason for the failure is that we started using the types_mapper keyword in pa.Array.to_pandas (previously this was ignored for arrays), but in this test it is passed a wrong values (it should be a callable, not a dict). Now, I think the argument can also just be removed.

[jrbourbeau]

Thanks @jorisvandenbossche! Would you mind pushing an empty commit with test-upstream in it? That will trigger a CI build which uses the nightly version of pyarrow here

[jorisvandenbossche]

The current upstream build is not actually using pyarrow dev (for some reason mamba is not selecting the nightly version, I looked at this before in the past (#8281), but not fully sure what's the reason for that)

[jorisvandenbossche]

Hmm, it seems we only have python 3.7 and python 3.10 packages in the nightlies, that is something to fix on the pyarrow side.

[jsignell]

We are also planning on adding Python 3.10 support to dask pretty soon, so at that point we will be able to update the upstream tests to use that. In the meantime I am going to merge this since it seems right from your explanation @jorisvandenbossche

[jorisvandenbossche]

Thanks. I am also working on getting the nightly packages back up for all python versions (apache/arrow#12492), once that is ready I will open a PR here to ensure we are using the latest pyarrow nightly in the upstream build.

[jrbourbeau]

Awesome, thanks as always @jorisvandenbossche