softethervpn5: Update libraries to fix 22.03 branch kernel incompatibility

[tew42]

Maintainer: ???
Compile tested: compiled for ath79 - Archer a7 v5 - OpenWRT 22.03.4 using the SDK in an Ubuntu 22.04 WSL environment
Run tested: ath79 - Archer a7 v5 - OpenWRT 22.03.4

Description:
As reported in #20807 the softethervpn5 libraries seem to have issues with keeping an open connection in 22.03 series builds, breaking module functionality. The root cause is not clear to me, though I'm guessing it's related to the newer kernel over 21.x. Regardless, building the package & libraries from a more recent upstream source code solved the issue.

Note 1: Seems like simple file editing on the website is insufficient for this commit, so re-started the whole thing with a proper git environment... Maybe now this will go better than my first attempts - sorry for the multiple requests.

Note 2: This patch should also be considered for master branch, but I can't really test on snapshot builds right now.

[tew42]

I'd appreciate any suggestions on how to properly get this to build, if it's even possible in this branch.

The core issue:

22.03 toolchain LibreSSL is missing required functions for softethervpn5 host compile. The requisite functions are of present in libopenssl - but that only helps for the target compilation part, not host.

Considered solutions:

1. I forced the compile for my own machine by eliminating the offending function check in the host compile -- and it works just fine for me. But that is really not ideal, and may break some package functionality for other use cases than my own.

2. Implement an openssl/host compilation in libopenssl Makefile. Probably the cleanest fix, but may create more problems than it solves beyond this specific case? Also perhaps overkill since the compile issue is solved in master/snapshot toolchain (newer LibreSSL).

3. A "dirty" solution I've considered would copy/paste the relevant libraries from $target/usr into /hostpkg, or alternatively mess around with CFLAGS/LDFLAGS. But I'm assuming that this would create some issues with cross-platform builds or something? (first time I'm dealing with something like this)

4. Leave the package "broken" in 22.03 branch, and implement the underlying version upgrade only in master/snapshot/23.xx, since the SSL dependency issue goes away there.

5. ???

[tew42]

Closed in favor of 23.x branch.