Attempt to guess the CI server from the URL

[GentlemanHal]

This will allow us to add specific parsing options for that particular CI server, currently this is only important for Go and Snap.

Now we always try and perform the Go/Snap specific parsing.

We could also just ask on the config screen but working it out automatically seems nicer if we can consistently.

[joejag]

So we would no longer get a {job: null, state: null} in the api calls when we use a Jenkins?

Are there any other benefits or bugs this would allow for?

[GentlemanHal]

Right now that would be the only obvious change.

Going forward I'd be surprised if Go/Snap where the only things that required some specific processing.

[joejag]

Yeah, I'd like to try out every CI server (that's where the Travis SSL issue came from), let's keep this issue open until we've tested with each.