Support piping of config files addressing.

This addresses issue #43 . As discussed in that issue thread, the next phase will be integrating sending of configs/content to the workers via IPC, but we could probably use a fresh issue for that. Also, the owner of parsons said he could not yet add in my change[implementing json parsing from a file pointer], because he is working on stuff in dev and planning on rolling out that feature later in October instead of right now. This is why this code implements file content extraction into a string and then the json gets parsed from it.
The only issue with that is, we can't tell whether (r == 0) is because an empty file was read in [no characters read in to begin with], or if EOF was encountered after reading a bunch of content. That is why there is a subsequent check for the offset. But for sure, I'll make it return the empty string which would match the agreed two states either "\0" or "....\0"