disable start_easy for error of which even google doesn't have a clue

https://travis-ci.org/PyMVPA/PyMVPA/builds/19780386
$ if [ ! -z  ]; then make coveragecmdline; fi
fatal: No names found, cannot describe anything.
I: testing start_easy cmdline example with coverage
ERROR: No value for objref '61682928' (LookupError)
make: *** [tcc-start_easy] Error 1
BF: no -e for elderly awk, and probably not needed
BF: correctly reconstruct nested dicts and lists with nasty self-references
BF: store is_objarray and shape, provide target container for objarrays

that first issue was introduced after 2.1.0 release, also tracking of id
was disabled for objarrays completely.
NF: MVPA_DEBUG_PDB to fall into debugger upon exception
ENH: do not fail logging if passed arguments fail to stringpolate
BF: if storing nested complex __reduce__'able objects -- __new__ instance first

Otherwise we cannot restore nested instances, which lead to our failures
and all this miss.  Solution is not elegant and more of a patch with
only hope that it would last -- time will show