EvseV2G: complete migration to libevse-security

[barsnick]

In commits 138b9db and dda60db, the EvseV2G module was converted to use libevse-security to locate the TLS certificates.

Yet there are still certificate paths for PnC which are (hard-) coded within the source code, e.g. here:

everest-core/modules/EvseV2G/iso_server.cpp

Lines 1226 to 1227 in d40971c

	std::string v2g_root_cert_path = conn->ctx->certs_path + "/ca/v2g/V2G_ROOT_CA.pem";
	std::string mo_root_cert_path = conn->ctx->certs_path + "/ca/mo/MO_ROOT_CA.pem";

For consistency, EvseV2G should be converted to use libevse-security here.

Additionally, EvseV2G could use libevse-security to verify client certificates (etc.), instead of using its own code. (Stage 2, nice to have.)

[corneliusclaussen]

I think that is something we also found at the cleveland testival, we tried something like this:

•        std::string v2g_root_cert_path = conn->ctx->r_security->call_get_verify_file(types::evse_security::CaCertificateType::V2G);
  

•        std::string mo_root_cert_path = conn->ctx->r_security->call_get_verify_file(types::evse_security::CaCertificateType::MO);
  

•        std::string v2g_root_cert_path = conn->ctx->certs_path + "/ca/v2g/V2G_ROOT_CA.pem";
  

•        std::string mo_root_cert_path = conn->ctx->certs_path + "/ca/mo/MO_ROOT_CA.pem";
  

However I think the CertificateTypes we are requesting are wrong in this example