STYLE: Use from future import annotations (pandas-dev#41901)
- [X] closes #41901
- [ ]  no tests added
- [ ]  pre-commit hook, no python files added
- [ ] No docstrings added; docs not rebuilt. _**Where do pre-commit hooks get added to “What’s New"?**_


Implementation:
   * Name set to always-use-future-annotations (rather than always-use-from-future-annotations)
   * We filter with` types: [python]` [rather than](https://pre-commit.com/#filtering-files-with-types) `files: "\\.(py)$”` 
   * No minimum pre-commit version. 

What else is needed here for a merge? 


edited comment to note that @aacosta13 has a script to add "from __future__ import annotations" to the 120 files in the codebase that currently don't have it (excluding tests, __init__.py, etc.) 

I suggested that should be a separate PR which can go in first.  @ForestMars yeah - can exclude asv_bench and web too though by way of update, I was waiting on a PR from @aacosta13 so that all targeted (ie. not excluded) files have the required import added, before we merge the pre-commit hook into the code base. I originally thought this was something that was going to be a quick fix, but haven't seen an update on #41901 in over a week.  This pull request is stale because it has been open for thirty days with no activity. Please update or respond to this comment if you're still interested in working on this. > by way of update, I was waiting on a PR from @aacosta13 so that all targeted (ie. not excluded) files have the required import added, before we merge the pre-commit hook into the code base. I originally thought this was something that was going to be a quick fix, but haven't seen an update on #41901 in over a week.

feel free to take over the other PR if you're still interested in working on this Thanks for the PR. As mentioned, it appears a precursor PR is needed first (which we're a happy to have from you) first. Since this PR has gone stale in the meantime, going to close for now.