MNT: Bump dev pin on NumPy
- [ ] closes #xxxx (Replace xxxx with the GitHub issue number)
- [ ] [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.

@mroeschke @WillAyd  - it will be a significant change to start returning Python objects instead of NumPy across the board. Do we want to make that (in separate PRs) before merging this? If it is a significant effort then I would say as long as we don't introduce new NumPy scalars in return values then we are good. We can leave it to separate exercises to hack away at that > as long as we don't introduce new NumPy scalars in return values then we are good

Right - this PR does not introduce any new instances of NumPy scalars, just adjusts the docstrings with the new repr as of NumPy 2.0. So prior to NumPy 2.0 these returned Python scalars but now they return NumPy scalars?  No, the same object is being returned - always a NumPy scalar. Only the repr is changing when you go from NumPy < 2 to NumPy >= 2. @Dr-Irv - friendly ping > @Dr-Irv - friendly ping

Sorry - I was out the past 5 days!  Will look now Thanks @rhshadrach 