BUG: tz_localize with ArrowDtype

[mroeschke]

• closes #xxxx (Replace xxxx with the GitHub issue number)
• Tests added and passed if fixing a bug or adding a new feature
• All code checks passed.
• Added type annotations 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.

[jbrockmendel]

is this copied from a non-pyarrow analogue? before too long we should really look at putting these in one place and parametrizing them

[mroeschke]

Nope, I came up with this example independently. It would be good to parameterize this with the existing tz_localize tests eventually.

[jbrockmendel]

comment on test org, otherwise LGTM

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout 2.0.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 ff8e88a05c907bd124bcfcf3c5384e16a7987cc7

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #52677: BUG: tz_localize with ArrowDtype'

4. Push to a named branch:

git push YOURFORK 2.0.x:auto-backport-of-pr-52677-on-2.0.x

5. Create a PR against branch 2.0.x, I would have named this PR:

"Backport PR #52677 on branch 2.0.x (BUG: tz_localize with ArrowDtype)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.