First steps for Neo4j driver.

 o Add cq as a linked in dependency.
 o Add hkp_neo.conf configuration file.
 o Add small note in readme about how to run with neo.
 o I've verified that this works to the point that the SQL commands
   executed generate syntax errors from Neo.
Disable all schema creation.

 o This means the server now starts and shows UI when backed
   by neo. Crashes when queried from syntax error.
 o We will want to re-introduce some constraints later on I think,
   specifically hockeypuck does a lot of work to de-duplicate
   entries, wich we should be able to get rid of by using a
   unique constraint and neo4js upsert command, MERGE.

   We'll also want some indexes, obviously.
First successful cypher query. 1/100000 done.
Insert public key into Neo

Missing the relationships.
Insert a UID into Neo4j

Does not handle relationships
Insert signatures
Insert a subkey into Neo4j
Handle existing signed keys

There is still a bug where we are using the keyid as the UUID in some places
instead of the fingerprint.
Expose the Neo4J and Hockeypuck servers
Fix order of parameters.
Translate UAT creation queries to Cypher.
A UID IDENTIFIES a PubKey
Match signatures to keys using the RKeyId

This allows a key's signatures to be imported, and later correctly matched
to the signing key when it is imported.

These are 16 character key IDs, so hopefully they won't collide.

The "R" in `RKeyId` means reversed. Because, of ... reasons.
Signatures as edges, not nodes.
Remove unused function.
Update key lookup from key ID.

I don't think we need to support the UNION from the original SQL query here:
They way we create SubKeys should mean that their corresponding PubKeys
always exist.