Unrecognized keys in pyproject.toml with pixi 0.41.1

[LucaMarconato]

Checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

pixi self-update --version 0.41.1  # or update with brew, ...
git clone https://github.com/spatial-image/multiscale-spatial-image
cd multiscale-spatial-image
pixi install -a

It will immediately fail. This is not a "minimal reproducible example" in the sense that I'm sure the bug could be reproduced with a smaller pyproject.toml file, but the above code will allow you to reproduce the bug in 1 second, via a single copy-paste.

Issue description

When instead I ran the same command on pixi 0.41.1 I immediately received this error:

(my_env) username@multiscale-spatial-image$ pixi install -a
Error: 
  × failed to parse project from /data/l989o/dependencies/multiscale-spatial-image/pyproject.toml: Unexpected keys, expected only 'name', 'version', 'description', 'readme', 'requires-python', 'license', 'license-files', 'authors', 'maintainers', 'keywords',
  │ 'classifiers', 'urls', 'entry-points', 'scripts', 'gui-scripts', 'dependencies', 'optional-dependencies', 'dynamic'

Instead, when I use pixi 0.39.5 the process works as expected (well, the process got stuck at "updating lock-file" and after 30 min I killed it, but this is not relevant in the context of this issue, and maybe it would be fixed in the latest version if the bug above didn't appear).

Expected behavior

The command pixi install -a should work and not complain about keys that should not be found in the pyproject.toml, since those keys worked in previous versions of pixi via pyproject.toml, and are still available when using pixi.toml with pixi 0.41.1 instead of pyproject.toml.

[Hofer-Julian]

If you check out the pyproject.toml specification, you'll find that project.home-page isn't a valid key: https://packaging.python.org/en/latest/specifications/pyproject-toml/#declaring-project-metadata-the-project-table

After removing that, pyproject.toml is sparsed just fine. I agree, though, that the error message isn't great.