update image version and do cargo fmt

Hi, this reminds me of #16 , where I explained why I did not want to use rustfmt or cargo fmt for this project.

I am not fundamentally against automated formatting, since it's great and many projects should be using it. However (and as explained in the linked issue), vek has many places which I don't want cargo fmt to touch.

In general also, in this commit, many one-liners were turned into like 4 or 5 lines or more; this reduces the amount of useful code that can fit in one screen.

The only good thing I see is that it sorts the use directives at the top of the modules, and removes some trailing spaces here and there.

I agree that automated formatting is great and that there is some mess that needs cleaning, however I would like it done "right", which requires just a bit too much effort (inserting #[rustfmt_ignore] in many places, tweaking various parameters, and really taking the time to review each file to make sure the formatting is still "good").

Furthermore, since it can be quite subjective, there can be a lot of back-and-forth until I say "looks good to me".

In general though, what I'm looking for is :

Code intended to be a one-liner remains a one-liner (this is true for function declarations, function bodies, etc)
Code that is specially arranged "visually" (as mentioned in #16 ) should remain the way it is.

I you can achieve that with cargo fmt then maybe I would consider it; but I wouldn't like to waste your time with that.
I found it simpler to accept the current formatting, imperfect as it is.

About the image update, yes we can do that! If we do, we also need to increment the patch version of vek.

yoanlcq / vek

update image version and do cargo fmt #83