Add failing test for pyarrow datetime merge issue

[Ayomide906]

Closes #61926

Summary

This PR adds a failing test case that reproduces a ValueError when merging two DataFrames with pyarrow-backed datetime columns using convert_dtypes(dtype_backend="pyarrow"). The test demonstrates the issue described in #61926 and is intended as a foundation for a future fix.

Due to build issues in Codespaces (related to Cython and pandas' compiled extensions), I focused on isolating the test logic. The test is wrapped in pytest.raises to explicitly capture the failure and document the bug.

Notes

• No fix is included yet — this PR is meant to validate and expose the bug, a fail-safe protocol.
• Maintainers or other contributors may want to build locally to explore a patch.
• Happy to follow up with a fix in the future or collaborate further once the build path is stable.

Checklist

• [x ] closes BUG: Merge fails on pyarrow datetime columns #61926 (Replace xxxx with the GitHub issue number)
• [ x] Tests added and passed if fixing a bug or adding a new feature
• [x ] 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]

This does not close the linked issue, and doesn’t use pytest.raises. This looks like AI slop, which is not welcome here.

[Ayomide906]

This does not close the linked issue, and doesn’t use pytest.raises. This looks like AI slop, which is not welcome here.

Oh Thanks , I did not intend to close the issue , This is my first contribution to open source, getting myself familiar with the environment but I am currently working on the issue who else is?

[simonjayhawkins]

Thanks for submitting this PR . We hope it’s been a useful learning experience as you get familiar with the pandas development process and CI environment.

Oh Thanks , I did not intend to close the issue , This is my first contribution to open source, getting myself familiar with the environment but I am currently working on the issue who else is?

I believe that @13muskanp is! see #62356 where a fix and a test is being working on - so we’ll close this for now.

Thanks again for your interest in contributing!