Refactor core action to return a parser instance based on the response body

Okay, seriously... It's the maintainers responsibility to ensure the gem doesn't go outside the scope of what it was designed for, and that the project doesn't become a collection of specific use cases, for specific applications. Logging originally wasn't a concern of conduit, however it made sense to log requests, so it was added. If conduits logging functionality has uses cases outside of conduit, it should be exported into another gem, and become a dependency on conduit. We shouldn't be adding functionality to allow third parties to tap into conduit logging, and bypass the rest of the system. At that point you're not using conduit, you're using conduit's logging.