Restrict mTLS security only to gRPC service scope

[Khertys]

Enabling mTLS currently breaks all APIs since it forces the user to provide a certificate, but browsers (REST, GraphQL APIs) don't support sending one. With the current implementation in the Armeria web server, we have trouble properly setting up mTLS for this purpose.

With version 1.31 (https://github.com/line/armeria/milestones) released, a new approach to TLS/mTLS configuration will be introduced. It should simplify our internal work with certificate security-related issues.

The release also contains necessary changes for easier solving #58

After this release, these features in eviteDB will be added/updated:

• correction of setting up TLS/mTLS in ExternalApiServer and the EvitaClient
• focus the mTLS restrictions only to mTLS supported APIs - gRPC
• certificate switching in runtime

[novoj]

@novoj will upgrade Armeria to server 1.31 which has improved work with TLS and will allow us to handle this issue in a more elegant way. @Khertys will then also fix and test the issue #58

[novoj]

I've ugpraded Armeria and other libraries to latest versions in branch version-upgrade. I've also attempted to prepare shaded client JAR that requires no dependencies. Can you please try it, and continue with mTLS reimplementation @Khertys?