DEPR: enforce a bunch
- [ ] closes #xxxx (Replace xxxx with the GitHub issue number)
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

@MarcoGorelli pls advise on the pylint failures, not clear if they are actionable probably not, do you want to add `c-extension-no-member` to

https://github.com/pandas-dev/pandas/blob/1d8922e20b3384d56551646dfbae2f4c4e458da0/pyproject.toml#L60-L78

alongside this PR? > pandas/core/frame.py:688:12: R1720: Unnecessary "else" after "raise", remove the "else" and de-indent the code inside it (no-else-raise)

Will this check start showing up in the pre-commit soon?  Otherwise let's get rid of it.  (and even if yes, im not a fan) yeah happy to get rid of it if you like - I'm glad that some of these pylint checks are helping find issue (like https://github.com/pandas-dev/pandas/pull/49382#pullrequestreview-1169896308), but others `no-else-raise` does seem nitpicky

EDIT: will review the rest of the PR this afternoon Thanks @jbrockmendel 