If a user requests to remove yin from the Absorber within the REQUEST_COOLDOWN period, the timelock for removal multiplies. 
This makes sense in case the user immediately requests again after a yin removal. However, the timelock is also multiplied in case the user accidentally requests again before a removal, which is simply unfair.
Only increase the timelock on request within REQUEST_COOLDOWN after a removal:
