curl: provide build-variants for each TLS implementation

[morytyann]

📦 Package Details

Maintainer: @

Description:

Let user can choose curl ssl backend by install different libcurl-* package.

This PR do 5 things:

1. remove libcurl package and remove the SSL library choice of libcurl.
2. add libcurl-nossl/libcurl-wolfssl/libcurl-gnutls/libcurl-openssl/libcurl-mbedtls which are provide libcurl
3. Remove the old libcurl-gnutls
4. migrate the depends (transmission/uacme/python-curl/php8-pecl-http) of SSL library choice.
5. migrate the depends (zabbix/gnunet) of libcurl-gnutls.

---

🧪 Run Testing Details

• **OpenWrt Version: SNAPSHOT
• **OpenWrt Target/Subtarget: x86/64
• **OpenWrt Device: VM

---

✅ Formalities

• I have reviewed the CONTRIBUTING.md file for detailed contributing guidelines.

[stangri]

@morytyann Hey Joseph, have you tested it with any packages previously using lubcurl-gnutls (ie: zabbix)?

[morytyann]

Yes, i made a image with all changed packages, and create a VM to test.

Here is the test result:

curl: works
python-curl: works (with demo file test.py)
php-pecl-http: works (with demo file test.php)
transmission: works
uacme: runnable
zabbix: runnable (zabbix-agentd)
gnunet: runnable (gnunet-arm)

Because i don't familiar with uacme/zabbix/gnunet, i don't know how to config or what parameter to use, i can't do a fully test, i just checked if it is runnable.