netty-tcnative dynamically links to older OpenSSL libraries when multiple versions are present

[chetangudisagar]

Netty Tcnative Version: 2.0.56.Final

OS Version -

$cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
...

OpenSSL Versions -

$sudo apt list --installed  | grep -i libssl

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libssl1.0.0/now 1:1.0.2zh***amd64 [installed,local]
libssl1.1/now 1.1.1f-1ubuntu2.19 amd64 [installed,local]
libssl3/now 1:3.0.8-***amd64 [installed,local]
$

Netty Server Logs -

 i.n.u.i.NativeLibraryLoader | Successfully loaded the library /image/***/temp/libnetty_tcnative_linux_x86_641637363384262540994.so
 i.n.u.i.NativeLibraryLoader | Loaded library with name 'netty_tcnative_linux_x86_64'
io.netty.handler.ssl.OpenSsl | Initialize netty-tcnative using engine: 'default'
io.netty.handler.ssl.OpenSsl | netty-tcnative using native library: OpenSSL 1.0.2zh-fips  30 May 2023

It should ideally discover and use the latest versions first instead of older versions.
I don't know if the discover strategy is find first or find last etc.

Could someone from the dev team check this and help?
Please let me know if any additional information is required.

What is the action plan to dynamically link to OpenSSL 3.0?