OpenKMIP
Update the client configuration file to match the server naming scheme
The client and server use different configuration names for the same certificate parameters (e.g., certfile vs certificate_path). This is an artifact of their separate development paths way back when. However, if a user misnames the client configuration parameters to match the server ones, the client TLS connection will fail with a non-intuitive certificate error (see #444).
Update the client configuration file to use the server naming scheme for certificate parameters, deprecating the old client names for these parameters to ensure a smooth migration period for users.
This came up again in Issue #448, this time regarding the host/hostname field, yielding an unintuitive client connection error.