TST (string dtype): un-xfail string tests specific to object dtype

[jbrockmendel]

xref #54792

[WillAyd]

I thought we added a hashtable for strings that didn't use Python objects. @phofl am I misremembering?

[jorisvandenbossche]

@WillAyd the StringHashTable is string specific, but still takes an object dtype array with Python strings as input (it just assumes the array only contains strings, and not any random Python object)

[github-actions]

This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this.

[jbrockmendel]

Still active

[jorisvandenbossche]

Thanks @jbrockmendel

[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 dbeeb1f05bca199b3c1aed979e6ae72074a82243

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

git commit -am 'Backport PR #59433: TST (string dtype): un-xfail string tests specific to object dtype'

4. Push to a named branch:

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

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

"Backport PR #59433 on branch 2.3.x (TST (string dtype): un-xfail string tests specific to object dtype)"

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.

[jorisvandenbossche]

Manual backport -> #60180