pkg/wolfssl: bump version to 4.3.0

[benpicco]

Contribution description

Update to the latest upstream release

https://www.wolfssl.com/docs/wolfssl-changelog/

Unfortunately the new version introduced some unused parameter warnings, so I disabled them for this pkg.

Testing procedure

I ran both tests/pkg_wolfssl and tests/pkg_wolfcrypt-ed25519-verify on native and esp32.

Issues/PRs references

none

[chrysn]

I know it's not required RIOT policy, but it's a Debian habit I'd consider useful here: Could you mention inside the patch where it was forwarded to upstream, if so, or whether it was cherry-picked from? That should help keeping track of patches we need to keep around as opposed to those we can get rid of eventually by being good downstreams.

[chrysn]

I've run the same tests on an nRF52840 (on the -dongle board), and they built and ran fine. I did not look into the changes in WolfSSL in particular other than skimming the change log, and there's nothing in there to indicate any downsides to an upgrade. Code size increase is, as expected, minimal (114k to 115k text for the self tests where increases might be expected, 23k by 8 byte increase for signature test).

[benpicco]

tbh the patch was a bit too messy to upstream and all the different compile-time config options make it hard to get this right.

But there is a much simpler solution that is employed by other pkgs too…

[MichelRottleuthner]

Tested on native and pba-d-01-kw2x with examples/dtls-wolfssl, tests/pkg_wolfcrypt-ed25519-verify and tests/wolfssl-test. All good, apart from examples/dtls-wolfssl but this is also the case on master.
Just one non-blocking suggestion below. ACK