MDLSITE-2689 determine if coding style problems detected

I just use a checksum of the 'blank' file here to determine it, which is a
great big hack, but quicker than refactoring the checker at this stage.
MDLSITE-2689 improve the prechecker wording a bit

I'm hacking hacking hacking here..

* Capture the full job output using the jira client
* Grep that output to find out if the smurf file detected any problems
* Display a different message depending on the circumstances
MDLSITE-2689 make branch part less noisy

Linking the whole branchname with a useful 'diff' url
Merge pull request #14 from danpoltawski/MDLSITE-2689

MDLSITE-2689 Reword a bit the messages from CiBoT
MDLSITE-3233 - fix message from cibot when repo not found

(Also made more cases get the -1 and error x)
Merge pull request #15 from danpoltawski/MDLSITE-3233

MDLSITE-3233 - fix message from cibot when repo not found
MDLSITE-3233 add informative link to code checker report
MDLSITE-3233 dan poltawski sucks!!!
MDLSITE-2662 fixed link capitlisation
MDLSITE-2966 add check for testing instructions
Merge pull request #16 from danpoltawski/MDLSITE-2966

MDLSITE-2966 add check for testing instructions