Update MethodInfo with the controller and method that really deal with the request

This is needed because when one controller method redirect or foward to another controller or another method, the MethodInfo remains with the original called method and not with the method that was last called.

For example, if we want to create a js and css renderer based on what controller and method has rendered the page, we need to know the method that rendered the request and not the method that was first called.
@lucascs @Turini Do you guys know why we did this? We update `MethodInfo` and then we rollback the change. I removed this behaviour to keep `MethodInfo`updated.