BUG: ArrowExtensionArray compared to invalid object not raising
- [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 an entry in the latest `doc/source/whatsnew/v1.5.1.rst` file if fixing a bug or adding a new feature.

would it make sense to have a code check for returning an exception rather than raising one?  (I think i wrote some methods a while back that intentionally return exceptions to be re-raised by callers which we'd have to change) > would it make sense to have a code check for returning an exception rather than raising one?

Did you mean raising exceptions rather than returning them? If so yeah it would help avoid cases like this and https://github.com/pandas-dev/pandas/pull/48834. `try/except` should be more reliable way to re-raise exceptions (specifically) rather than using `return`?

 Thx @mroeschke 