Create configure --enable-SPKG options also for pip packages

[mkoeppe]

• This reverts Remove ./configure --enable-SPKG options for pip packages (for which this is not implemented) #29626, which was intended as a hot fix only
• Follow up to build/make/Makefile.in: Rename make targets SPKG-clean to SPKG-uninstall #29097
• Addresses https://groups.google.com/g/sage-devel/c/qnqBC2ybR3U @enriqueartal @dcoudert

📝 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

[github-actions]

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

[kwankyu]

I tested with ./configure --enable-pycryptosat. This worked. That is, make installed the package:

[pycryptosat] Installing collected packages: pycryptosat
[pycryptosat] Successfully installed pycryptosat-5.11.21

But the message from ./configure --enable-pycryptosat is not appropriate:

pycparser:                      no; standard, SPKG version 2.22 is already installed
pycryptosat:                    no; optional pip package; use "./sage -i pycryptosat" to install
pygments:                       no; standard, SPKG version 2.18.0 is already installed

This message persists even after make installed pycryptosat successfully.

[mkoeppe]

Right. For pip packages, the Sage distribution does not maintain installation records (other than pip's own records), and the configure script (nor the build system) does not know what is installed.
I'll adjust the messages accordingly.