[BUG] Failed to initialize netty-tcnative

[Chillax-0v0]

In allocation flame graph:

Netty SSL uses the default engine which uses heap buffers:

�
However, it's better to use OpenSSL said in AWS SDK best practices

Then I enabled DEBUG logs and got:

In Netty's doc it says:

The maven packaging changed a bit in version 2.0.49.Final. The changes were fine for Maven users, but causes some trouble for Gradle and Bazel users.
For Gradle, the solution is to explicitly declare the tcnative dependencies with classifiers.

(see also netty/netty-tcnative#716 for details)

So this issue is caused by #1010 (also #1014) which upgrade netty-tcnative-boringssl-static from 2.0.48 to 2.0.65.

We can fix this by adding classifiers as the doc says, and here's an example grpc/grpc-java#9027