making "Signed" RDF fingerprints
In order for RDF fingerprints that represent things like hyrdogen bonding, product of charges, etc to make sense, we need to keep track of the "sign" of the function.
Specifically, a case where partner A is a hydrogen bond donor and partner B is an acceptor is a fundamentally different signal than hte reverse case. So the RDF code has been rewritten to accomodate this.
additionally, a few bugfixes to the ligand highres docker code
hts_io integration test changes
all unit tests pass