BLD: relax meson/meson-python requirements
This makes bugfixes from later meson/meson-python fixes available to build pandas. For eg: python 3.13t support in meson, needs an up-to-date version of meson.

- [ ] 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.

cc @rgommers 
Thanks for the PR.

I'm OK with bumping, but I'd prefer leaving the pin in.
(This has "protected" us from bugs/breaking changes in the latest meson in the past.)

CI looks to be just red in general across pandas unfortunately. 
(If someone doesn't fix the failing builds over the next couple of days, I'll go ahead and take a look myself.) > I'm OK with bumping, but I'd prefer leaving the pin in.
> (This has "protected" us from bugs/breaking changes in the latest meson in the past.)

Hard pins in general are never the right thing to do in `main` (unless the dependency is too unstable, which meson/meson-python are not), so if you really want to keep an `==` then I suggest:
1. Put a comment above it that this is a pre-emptive pin only, and distro maintainers can feel free to drop the pin
2. Amend your release procedure to bump the pinned version to the latest released one before each release.

If you don't do that, you will end up creating problems for distros, as well as missing out on lots of bug fixes which tend to be needed for users on niche platforms and niche compilers in particular. Also +1 to remove the pin. I think it was really useful when we swapped over to Meson, but its probably outlived its usefulness. I've used Meson on a few other projects with only setting a minimum bound, and haven't run into issues.  CI is fixed now, can you merge main. Thanks @isuruf 