BUG: DataFrame.shift(axis=1) with EADtype
- [ ] closes #xxxx (Replace xxxx with the GitHub issue number)
- [x] [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.
- [x] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

Following this we can simplify the Manager/Block/EA methods since they will only ever get `axis=0`
Thanks @jbrockmendel  Thoughts about deprecating this first? This is not great for Dask for example, since users won't be able to use older versions of dask with the new pandas version since the default for us is None which will raise

cc @jbrockmendel  No objection to doing this as a deprecation first (i.e. #54818)