Pin fastparquet
- [ ] xref #42588
- [ ] tests added / passed
- [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [ ] whatsnew entry

Get CI to green.
Should probably pin in requirements-dev.txt as well until it is ready to move to 0.7.0. The fastparquet tests also fail on 1.3.x, so milestone 1.3.1 to trigger backport @lithomas1 can you open an issue to unpin this. > @lithomas1 can you open an issue to unpin this.

added xref to the issue to the op, so no need to open a separate issue. @github-actions pre-commit Green, can someone from @pandas-dev/pandas-core merge?

Sorry about the noise in this PR, was using the Github Web UI, which pre-commit apparently doesn't like.

Windows py39 is unrelated timeout. Windows py38 & Database are the only builds that matter in this case. Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

```
$ git checkout 1.3.x
$ git pull
```

2. Cherry pick the first parent branch of the this PR on top of the older branch:
```
$ git cherry-pick -m1 46ed60a2cb007276b38f0bcdead312d95cfc4d54
```

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

```
$ git commit -am 'Backport PR #42612: Pin fastparquet'
```

4. Push to a named branch :

```
git push YOURFORK 1.3.x:auto-backport-of-pr-42612-on-1.3.x
```

5. Create a PR against branch 1.3.x, I would have named this PR:

> "Backport PR #42612 on branch 1.3.x"

And apply the correct labels and milestones.

Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon!

If these instruction are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
                 thx @lithomas1  backported manually thx @phofl. 