BUG: drop_duplicates raising for boolean arrow dtype with missing values
- [x] closes #54667 (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
- [x] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [x] 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.

cc @mroeschke 

More generally, how do we want to proceed with Arrow EA fixes after 2.1 is out?
> More generally, how do we want to proceed with Arrow EA fixes after 2.1 is out?

Since Arrow support isn't new anymore I suppose we shouldn't be backporting bug fixes as aggressively anymore, but I would still be okay with it Ok then maybe lets backport low risk fixes and decide on the others on a case by case basis Thanks @phofl 