Update all proximal operators in place

[fred3m]

No description provided.

[pmelchior]

All changes are OK. However, I wonder if we still need to inline change, which is at least somewhat unexpected. We introduced that to allow on-the-fly resizing without interrupting the algorithms in this package, and we're not using this feature any more. The more transparent approach would be to return the modified variable but leave the original intact. Plus, if we actually want to differentiate through those proxes, we couldn't do inline updates either.

So the question here is, should we use this PR to make that change?

[pmelchior]

Ignore request, this should be an independent PR.

[fred3m]

While the other approach would be more transparent there are a few things that we need to consider:

• This approach would use more memory, and in light of Check unnecessary copies of data structures scarlet#101 I think we all want to do a better job managing our memory use
• If we start applying our proximal operators inside the gradients we need to be very careful about how we do this. autograd doesn't like inline updates, but I'm also not sure how it would respond to rewriting the entire array it is using for the gradient. This makes me think that we should add a few more tests to scarlet to make sure that proximal operators and autograd are compatible (which they likely aren't in their current or proposed state).