BUG/MEDIUM: jwt: Use JWT cert tree for jwt_decrypt
The jwt_decrypt converters have the same issue as the jwt_verify one,
they were taking the ckch_lock during runtime processing which could
fail in case the lock was already taken by a CLI operation.
We now make use of the already existing jwt tree to store the private
keys used in the decrypt operations. The only lock taken during runtime
is the jwt tree one which also gets locked in write mode while updating
certificates via the CLI or changing the jwt mode ("add/del ssl jwt").
This patch is a continuation of "BUG/MEDIUM: jwt: Use only JWT cert tree
for jwt_verify", it helps fix for good the issue decribed in GitHub
issue #3526. It relies on "MINOR: jwt: Add rwlock to jwt_cert_tree" as
well.