Azure CI: don't force non-existing OpenSSL configuration anymore
    
    Newer grunt will pull a PhantomJS that is compatible with newer OpenSSL
    so the workaround is not needed anymore.
    
    Additionally, OpenSSL 3.0 is more strict and does not tolerate
    non-existing default configuration file.
    
    Signed-off-by: Alexander Bokovoy <abokovoy@redhat.com>
    Reviewed-By: Florence Blanc-Renaud <frenaud@redhat.com>