fix filesystem connector jcr:content fix, add options for increased bina...

1) FileSystemConnector was using a id of parent (nt:file) rather than content (jcr:content) putting jcr:content properties in nt:file properties. JsonSidecarExtraPropertiesStorage wasn't distinguishing between file or content.  Fixes to this MODE-2060

2) 2 new options within extraSources when using FileSystemConnector as classname:
  a) opensslDeployment - path to openssl binaries installation
  b) hashMode - 
      i) missing or "default" - check binary key as is
      ii) "cached" - binarykey only computed once, stored in HashMap, uses opensslDeployment if configured
      iii) "mocked" - binary key created from filepath rather than file content
Features MODE-2061

stats for retrieving jcr:content node of 1.3GB and 64GB file:
default modeshape secureHash - 12 sec/16.6 minutes
cached openssl - 3.5 sec/8.1 minutes
cached modeshape secureHash - 6.2 sec/8.1 minutes
mocked - .002 sec