CP-7292: Make use of the exit code of pylint
CP-7292: Make use of the exit code of pylint

In the previous version of pylint we use, the exit code of a pylint
process is always zero (regardless there are issues found or not).
So we have to capture the output of pylint to make a judgement call
ourselves.

The newer vesion of pylint exit with non-zero code if any issue
has been found. So we can now interpreter the exit code rathe than
the output text, which makes things simpler.

Unfortunately, a bug in the exact version 0.21.1 [1] stops us from
passing all the python files to check to pylint all at once, so we
still have to iterate over all the files one by one and record the
existence of any errors. The code can become considerablly simpler
when we move to a even newer version of pylint with this bug fixed.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591670

Signed-off-by: Zheng Li <fff69bf00b8ec5b6098a1768eaaaa75f40b8795d@eu.citrix.com>
Reviewed-by: Chandrika Srinivasan <51ae5eeda27fe08017d2d63c87755f0707891830@citrix.com>

djs55/sm,malcolmcrossley/sm,pritha-srivastava/sm,xapi-project/sm,siddharthv/sm,BobBall/sm,martinjorge/sm,kostaslamda/sm,germanop/sm,siddharthv/sm,BobBall/sm,djs55/sm,germanop/sm,xapi-project/sm,chandrikas/sm,kostaslamda/sm,robertbreker/sm,geosharath/sm,pritha-srivastava/sm,siddharthv/sm,martinjorge/sm,robertbreker/sm,pritha-srivastava/sm,geosharath/sm,germanop/sm,BobBall/sm,kostaslamda/sm,malcolmcrossley/sm,chandrikas/sm,martinjorge/sm,malcolmcrossley/sm,geosharath/sm,chandrikas/sm,robertbreker/sm,xapi-project/sm,djs55/sm