Use meson-python main branch

[jarrodmillman]

See #6667

Description

Checklist

• Docstrings for all functions
• Gallery example in ./doc/examples (new features only)
• Benchmark in ./benchmarks, if your changes aren't covered by an
  existing benchmark
• Unit tests
• Clean style in the spirit of PEP8
• Descriptive commit messages (see below)

For reviewers

• Check that the PR title is short, concise, and will make sense 1 year
  later.
• Check that new functions are imported in corresponding __init__.py.
• Check that new features, API changes, and deprecations are mentioned in
  doc/release/release_dev.rst.
• There is a bot to help automate backporting a PR to an older branch. For
  example, to backport to v0.19.x after merging, add the following in a PR
  comment: @meeseeksdev backport to v0.19.x
• To run benchmarks on a PR, add the run-benchmark label. To rerun, the label
  can be removed and then added again. The benchmark output can be checked in
  the "Actions" tab.

[dnicolodi]

I don't think this is enough to make cibuildwheel use meson-python from git. The easiest is probably to patch pyproject.toml's [build-system] section.

[stefanv]

@jarrodmillman also see the branch I pushed to maintenance last night.

[dnicolodi]

@stefanv Your approach does not work with cibuildwheel either. Patching pyproject.toml is really the easiest solution

[dnicolodi]

The correct syntax is meson-python @ git+https://github.com/mesonbuild/meson-python. I would also pin the version, in case future commits to the meson-python git repository break something:

meson-python @ git+https://github.com/mesonbuild/meson-python@babdf709618fbeeaf59634bc2b4331ca5f7924ce"