TST: filter possible RuntimeWarning in tests

[mroeschke]

I'm unsure why the OSX 13, Python 3.10 & 3.11 jobs are just complaining about an invalid value in cast from .astype of a ndarray of exotic types like interval to str (and then object), but I think generally we should be safe to ignore this.

e.g. https://github.com/pandas-dev/pandas/actions/runs/12286515835/job/34286806506

[mroeschke]

Going to merge to get the CI closer to green

[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.3.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 c52846ff94d51ce5940928c199da00f403bc8138

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

git commit -am 'Backport PR #60553: TST: filter possible RuntimeWarning in tests'

4. Push to a named branch:

git push YOURFORK 2.3.x:auto-backport-of-pr-60553-on-2.3.x

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

"Backport PR #60553 on branch 2.3.x (TST: filter possible RuntimeWarning in tests)"

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.