test/provider: Explicitly initialize OpenSSL after setting env vars.

When running with a libica version without commit
opencryptoki/libica@42e197f
it is necessary to explicitly initialize OpenSSL before loading libica. Because
otherwise libica's library constructor will initialize OpenSSL the first time,
which in turn will load the IBMCA provider, and it will fall into the same
problem as fixed by above libica commit, i.e. the provider won't be able to
get the supported algorithms from libica an thus will not register any
algorithms.

Signed-off-by: Ingo Franzki <ifranzki@linux.ibm.com>

Author: ifranzki

test/provider/dhkey.c

@@ -461,6 +461,8 @@ int main(int argc, char **argv)
         return 77;
     }
 
+    OPENSSL_init_crypto(OPENSSL_INIT_LOAD_CONFIG, NULL);
+
     ret = check_libica();
     if (ret != 0)
         return ret;

test/provider/eckey.c

@@ -895,6 +895,8 @@ int main(int argc, char **argv)
         return 77;
     }
 
+    OPENSSL_init_crypto(OPENSSL_INIT_LOAD_CONFIG, NULL);
+
     ret = check_libica();
     if (ret != 0)
         return ret;

test/provider/rsakey.c

@@ -839,6 +839,8 @@ int main(int argc, char **argv)
         return 77;
     }
 
+    OPENSSL_init_crypto(OPENSSL_INIT_LOAD_CONFIG, NULL);
+
     ret = check_libica();
     if (ret != 0)
         return ret;