Reverting back to sample conf/dev_authentication.conf

This is easier for quick development. Anything more complex really only takes
place in deployment and should be controlled at the system level by puppet.

When actually developing changes to how these files are used by the auth layer,
then requiring the author to remember to not commit them feels simpler than
having every collins developer need to maintain an untracked
dev_authentication.conf