Omniconf implementation

[RandomGuyOnTheInternet1234]

This pull request implements omniconf configuration to store variables about where the git repos are located. Also, I fixed the bug where I couldn't run the code in a directory with a space.

[dgopstein]

Thanks for the PR, it's looking pretty good! Some comments:

• I don't know if you saw but this change has "merge conflicts" which means that the version of the code you were working from got changed in the meantime and so git doesn't know how to apply your changes anymore. In order to fix this you need to do a git mergetool. Sometimes this can be a real hassle, but in this case I think the conflicts are pretty minor.

• Instead of needing to import omniconf.core, and remember the name of the conf file and the settings in that conf file for every access, can you just use your conf code to populate the values in constants.clj one time? And leave the references to gcc-path, the way they were in the code before. This should end up being a much smaller diff, and make it much easier to use these values in the future.

• Don't put :jake-dev-conf in the codebase since me and Henry and anyone else will want our own settings as well. Instead the code should be perfectly generic, and the only thing that changes from my machine to yours is which conf file we use. I can have dan.edn and you can have jake.edn, but inside they all have the same structure with different variables. And from there we can each symlink our own conf to the general conf.edn. Or something.

• Probably the conf files should live in src/conf or something instead of at the root level, since there will likely need to be a bunch of them.

[dgopstein]

Can you remove this?