Building wheel fails using latest rust toolchain

[zzzeid]

Due to recent breaking change in maturin (PyO3/maturin#1047) building wheel fails, as project metadata is still present in Cargo.toml. It should be moved to pyproject.toml (see PEP 621).

$ pip install rs-parsepatch==0.3.7 --no-binary :all:
DEPRECATION: --no-binary currently disables reading from the cache of locally built wheels. In the future --no-binary will not influence the wheel cache. pip 23.1 will enforce this behaviour change. A possible replacement is to use the --no-cache-dir option. You can use the flag --use-feature=no-binary-enable-wheel-cache to test the upcoming behaviour. Discussion can be found at https://github.com/pypa/pip/issues/11453
Collecting rs-parsepatch==0.3.7
  Using cached rs_parsepatch-0.3.7.tar.gz (117 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... error
  error: subprocess-exited-with-error
  
  × Preparing metadata (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [5 lines of output]
      💥 maturin failed
        Caused by: The following metadata fields in `package.metadata.maturin` section of Cargo.toml are removed since maturin 0.14.0: classifier, maintainer-email, project-url, please set them in pyproject.toml as PEP 621 specifies.
      Error running maturin: Command '['maturin', 'pep517', 'write-dist-info', '--metadata-directory', '/private/var/folders/mz/dt2wvcqn2v18chcgg04003k40000gn/T/pip-modern-metadata-dwao3msm', '--interpreter', '/Users/zeid/src/env/bin/python3.10']' returned non-zero exit status 1.
      Checking for Rust toolchain....
      Running `maturin pep517 write-dist-info --metadata-directory /private/var/folders/mz/dt2wvcqn2v18chcgg04003k40000gn/T/pip-modern-metadata-dwao3msm --interpreter /Users/zeid/src/env/bin/python3.10`
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Edit: using Python 3.10 on macOS 13 (M1)