Remove workarounds for packages that use flit_core or poetry_core as build system #32483
Description
These workarounds were added in #29803.
$ git grep -B 3 'rm.*pyproject'
build/pkgs/entrypoints/spkg-install.in-# Make sure that modern pip uses the generated setup.py
build/pkgs/entrypoints/spkg-install.in-# that is distributed with the PyPI tarball,
build/pkgs/entrypoints/spkg-install.in-# so we do not have to have flit. Trac #29803.
build/pkgs/entrypoints/spkg-install.in:rm -f pyproject.toml
--
build/pkgs/pkgconfig/spkg-install.in-# Make sure that modern pip uses the generated setup.py
build/pkgs/pkgconfig/spkg-install.in-# that is distributed with the PyPI tarball,
build/pkgs/pkgconfig/spkg-install.in-# so we do not have to have poetry. Trac #29803.
build/pkgs/pkgconfig/spkg-install.in:rm -f pyproject.toml
--
build/pkgs/terminado/spkg-install.in-# Make sure that modern pip uses the generated setup.py
build/pkgs/terminado/spkg-install.in-# that is distributed with the PyPI tarball,
build/pkgs/terminado/spkg-install.in-# so we do not have to have flit. Trac #29803.
build/pkgs/terminado/spkg-install.in:rm -f pyproject.toml
--
flit_core is added in #31280, poetry_core in #33866, so we can make use of these build systems instead of relying on generated setup scripts.
Depends on #33530
Depends on #33789
Component: build
Author: Matthias Koeppe
Branch/Commit: 1079cd4
Reviewer: John Palmieri
Issue created by migration from https://trac.sagemath.org/ticket/32483