Xval

This revives #235. Now that all the other elements are in place, I think that this is ready for review and in principle ready to be merged upstream (once it's been reviewed and fixed up, of course!). I am excited about this PR - evaluation of DWI models is something that I have been thinking a lot about in the past couple of years, since I started working on DWI. 

This PR also demonstrates the power and elegance of the uniform `Model`/`Fit` API we have in place. GGT!

For now, this PR only implements cross-validation for CSD and for the tensor model, but future work could extend this to other models, by implementing their `predict` methods. 

Also : a lot of PEP8 fixes in the CSD module and elsewhere :-) 
Well... @stefanv may have a different opinion on that. Also this rule makes sense for C code but not for Python. 

I personally think that when classes are defined at the top it is easier to get to the most important parts of the code faster. The CSDModel is a good example.
But because people reviewing my code have asked me in the past to put classes' 
definitions at the top and I started using this style... I saw the benefits myself and 
I wanted to share this experience with you too.