Extra noise in controller's input covariance about pilco HOT 2 OPEN

I don't see how this is necessary. I guess the original authors found it helpful empirically, maybe for numerical stability etc. Since there might be other design choices like this one, that look arbitrary, I think could do either of two things:

1. Keep them in our code too, to be consistent with the original application, and assuming that these were found to be beneficial to the algorithm's performance
2. Not add them if we don't see the benefit, but keep track of them somehow, so in the case we end up having numerical or other issues on a future scenario, we can try adding things from the list.

I think 2 is reasonable, in a sense we are already doing it by not adding any trigonometric augmentation of dimensions that are angles for example, and it keeps our code cleaner until it's necessary to complicate things further.

from pilco.

Let's do this, at least for the sake for compatibility.

from pilco.