(MAINT) Feature/curl retries

This seems to force the number of retries regardless of whether a test explicitly asked for it or not. I assume you need this for something to do with the startup time of the JVM puppetmaster? If so, would it be possible to load the retry number closer to where that service management is being done?

When doing integration testing of JVM puppetmaster with the rest of the PE stack, I don't really like the idea of the retry count for, say, puppetdb being overridden by the hosts file just because it is needed by the puppetmaster