TST: Fix unsigned pyarrow types in SIGNED_INT_PYARROW_DTYPES
- [x] closes #48471 48471
- [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.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.

Thanks @gsheni, is there an issue for this? Can you please provide context about this? Thanks for the pull request, but when implementing this I did not specifically include testing `pa.string()` because pyarrow string functionality still fully exists in `StringDtype("pyarrow")` and `ArrowStringArray`. This note will be in the 1.5 docs: https://pandas.pydata.org/docs/dev/reference/arrays.html#pyarrow

What would be helpful is to start an issue to discuss whether there's interest to have `ArrowDtype(pa.string())` replace `StringDtype("pyarrow")` in the future. @mroeschke sure, issue created here: https://github.com/pandas-dev/pandas/issues/48469

It might be worth reviewing this MR, as the `SIGNED_INT_PYARROW_DTYPES` list has incorrect data types. > It might be worth reviewing this MR, as the SIGNED_INT_PYARROW_DTYPES list has incorrect data types.

Yes those fixes would be welcome! Hello @gsheni! Thanks for updating this PR. We checked the lines you've touched for [PEP 8](https://www.python.org/dev/peps/pep-0008) issues, and found:



There are currently no PEP 8 issues detected in this Pull Request. Cheers! :beers: 

##### Comment last updated at 2022-09-12 22:05:40 UTC @gsheni mind merging main? Don't remember if these failures were real or unrelated `test_add_series_with_extension_array` might need an xfail Thanks @gsheni 