Build metadata fixes 10.8.beta2

[dimpase]

correct version constraints for pybind11, add gentoo package info for python-build

📝 Checklist

• The title is concise and informative.
• The description explains in detail what this PR is about.
• I have linked a relevant issue or discussion.
• I have created tests covering the changes.
• I have updated the documentation and checked the documentation preview.

⌛ Dependencies

[dimpase]

to ensure smoother ride on Gentoo in particular

[github-actions]

Documentation preview for this PR (built with commit 3742ec6; changes) is ready! 🎉
This preview will update shortly after each push to this PR.

[orlitzky]

I haven't run ./bootstrap && ./configure in a very long time, but I'll take your word for it. I guess this could go wrong if you have pybind-3.0 but try to install scipy from the SPKG? Either way this is probably better for the people who are trying to use system python packages.

[dimpase]

I haven't run ./bootstrap && ./configure in a very long time, but I'll take your word for it. I guess this could go wrong if you have pybind-3.0 but try to install scipy from the SPKG? Either way this is probably better for the people who are trying to use system python packages.

scipy says:

    # The upper bound on pybind11 is pre-emptive only

[vbraun]

With this the build fails at gmpy2 for me (after make distclean)

[spkg-install] Installing gmpy2-2.2.0a1
[spkg-install] /home/release/Sage/local/var/lib/sage/venv-python3.12.5/bin/python3: No module named build
[spkg-install] Warning: building with "python3 -m build --wheel --outdir=dist   ." failed.
[spkg-install] Retrying with "python3 -m build --wheel --outdir=dist --no-isolation --skip-dependency-check  .".
[spkg-install] /home/release/Sage/local/var/lib/sage/venv-python3.12.5/bin/python3: No module named build
[spkg-install] ***************************************************************************************************************************************************************************
[spkg-install] Error building a wheel for gmpy2-2.2.0a1
[spkg-install] ***************************************************************************************************************************************************************************
************************************************************************
Error installing package gmpy2-2.2.0a1
************************************************************************

[dimpase]

@vbraun please post config.log for this build, or at least provide me an access to it

[dimpase]

@vbraun - I suppose it might need #39364 - on which you stall, for some reason for like a month. Ping?

[vbraun]

I don't think its specific to gmpy2, thats just the first package that fails. After that many other python packages will fail with the same error. Build is not installed or there is something wrong with the python path and it gets confused with the "build" directory.

[dimpase]

Sorry, we just should revert 59df82b - it was OK without it.

[dimpase]

the rest is totally non-controversial, setting to positive

[dimpase]

On opensuse tumbleweed CI runs one gets 21.15 Package 'python310-setuptools' not found.
I guess it's due to python3${PYTHON_MINOR}-setuptools in build/pkgs/setuptools/distros/opensuse.txt - and apparently it's not right for umbleweed (not sure about other flavours of suse).

[dimpase]

tests pass (there are 2 false positives). I move it back to positive review after a trivial rebase