Various optimizations on reapplication of pending transactions

The changes include:

• quality of life + optimization for expired transactions - they are now just counted, so especially during high traffic when there might be many such pending transactions hived no longer generates massive amount of log messages
• cheap version of much broader optimization - pending transactions no longer validate compound operations, since that is one on transaction invariants (does not depend on state) - such check was done when the transactions became pending (and will be performed again when they are to be included in block - at least for now); also authorization verification is skipped, since situation when it would fail is extremely rare, so the only drawback from skipping it here is that such transaction will longer be reported as valid, despite the fact that in the end witness will drop it; on positive side we gain a lot in terms of performance