Using `bytes` options for TLS rather than `path` does not appear to work

[leonardb]

FDB allows for:

tls_ca_path tls_ca_bytes tls_key_path tls_key_bytes tls_cert_path tls_cert_bytes

When erlfdb inits using the path env values I can connect to the cluster and use the DB. If I use the bytes options erlfdb 'seems' to connect and returns a database when erlfdb:open(Cluster)., but all further operations just hang. A simple transactional set ends up stuck in erlfdb:wait and never returns.

The only error I see in the fdb trace logs is a 1026 network error which is of course helpfully undocumented.

Rationale: I currently have a branch which does a lazy init of erlfdb_nif and passes in the network options as they are pulled from a key server on init of the parent application. Currently I'm having to store keys to disk and pass in the path variants, but would definitely prefer that keys do no get saved to disk at all.