API clients only support one server certificate at a time

I have written a simple python API client app to look up historic flowcell check results across multiple P2-solo hosts.

Unfortunately each of these minknow instances seems to use a secure channel with its own self-signed certificates and the python API client library only allow one ca.crt to be read at runtime via the MINKNOW_TRUSTED_CA environment variable.

According to #77 these certificates are regenerated at boot and daily (though only picked up when Minknow service restarts), and seems to ignore the application_conf configured cert path. This isn't very easy to unpick for anybody starting to write remote API client tools! (Please can you improve the docs for remote connections?)

The quickest fix I can see is to replace the certificates with my own single cert shared across all instances and clients and disable rpc-certs-gend.service. Is that what ONT recommend or are they likely to change things again before #77 is fixed?

Start by reading issue #77 and tracing how MINKNOW_TRUSTED_CA, application_conf, and rpc-certs-gend.service relate to remote connections. Determine whether multi-host certificate support or clearer remote-connection documentation is intended; done should include an agreed supported setup and corresponding guidance.