Fixed placement of remove_expired_governance_votes call

Call to remove_expired_governance_votes was incorrectly placed before current block updated its date, which resulted in vote expiration happening not at block with given expiration data as its timestamp, but at the beginning on next block. It was fixed by moving the call to the end of block. In practice this change mostly influences tests where vote expiration now behaves like every other feature, where you need to run to the block with specific timestamp to get the result. Previously in case of vote expiration (and only in that case) you needed to produce one more block.