Use time() instead of REQUEST_TIME for Commerce entity saves

Moving this to needs review.

I have applied the patch, reviewed the code and ran through the checkout. it is grabbing the time via time(). So far so good. Times have come in correctly on all my trial runs. Thumbs up for me, unless anyone has more tests I can run.

I wonder, why is it using yet another variable here, $current_timestamp. It shouldn't be using time() in all places?

Successfully tested and reviewed the code in #1.

I wonder, why is it using yet another variable here, $current_timestamp. It shouldn't be using time() in all places?

That way it is consistent through the one method invocation? Perhaps? Either way, PHP time() returns seconds and not microseconds, to it will probably be the same. This way it is at least properly updated for each method invoke.

You know what, I wonder if we shouldn't generalize this patch and do the same in all of our entity controllers. Or are we maintaining payment transactions are just a special case?

+1 #8. Let's update all the things. This would be great for orders.

I suppose the only thing we need to ensure is that an updated entity with revision supports always uses the same updated timestamp as its revision's created timestamp.