COMPAT: Matplotlib 3.5.0
- [ ] closes #44521 
- [ ] tests added / passed
- [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit) for how to run them
- [ ] whatsnew entry

Still some deprecation warnings left. Anyone want to approve for me so we can get this merged ASAP?
we are fully testing i assume?

can u add. what's new note for 1.3.5 re-started the timed-out build.  one question about the ax.grid(False), otherwise LGTM pending green(ish) gets us back to green on everything except the docbuild.  @jreback good to go? yep merge when ready thanks @lithomas1  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 8b2477dac4dac603e80ef6c8de254f094b8ab801
```

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

```
git commit -am 'Backport PR #44523: COMPAT: Matplotlib 3.5.0'
```

4. Push to a named branch:

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

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

> "Backport PR #44523 on branch 1.3.x (COMPAT: Matplotlib 3.5.0)"

And apply the correct labels and milestones.

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

Remember to remove the `Still Needs Manual Backport` label once the PR gets merged.

If these instructions are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
                 > can u add. what's new note for 1.3.5

did we want a release note for this?