The jwt_cert_tree that stores pure public keys loaded during init and is
used by the jwt_verify converter was never locked since we only appended
entries during init and never modified them during runtime.
In future commits its usage will be extended so it will need a locking
mechanism. The tree will only change following CLI updates so a rwlock
should do the job since mos of the work will be done under a read lock
only.