Correctly responds to inactive update puller

There are different use cases for the update puller. Some cases are OK
with observing the puller becoming inactive while awaiting the condition,
others aren't. This different existed already, but only as a check before
the call and inside await an exception was thrown when this happened. This
commit moves the difference in handling an inactive puller into await
where the caller can decide how to handle it.
Log rotation won't happen on kernel panic

Log rotation checks that the kernel is still healthy, while having the
logFile lock, before doing the rotation. This to be on the safe side in
the event of panic, ehere the next recovery will have a chance to repair
the damages if all transactions are still in the active log.

For this the TransactionAppender#append method decides on success or panic
while holding the logFile lock and therefore safely communicates this
state to any log rotation happening concurrently.
Make sure that Table-bound resources are released when a primitive collection is closed
Fix an use-after-statement-closed error with USING PERIODIC COMMIT
Equals and hashCode for primitive collections

Also fixes the PrimitiveIntLongVisitor and PrimitiveIntLongMap.visitEntries, such that visitation can throw custom exceptions or be halted midway.
Merge pull request #3701 from tinwelint/2.2-dont-rotate-on-failure

Log rotation won't happen on kernel panic
Merge pull request #3706 from jakub-/user-after-statement-closed

Fix an use-after-statement-closed error with USING PERIODIC COMMIT
Merge pull request #3702 from chrisvest/2.2-prim-coll-eq

Equals and hashCode implementations for the primitive collections
Merge 2.1-maint in master
Merge pull request #3696 from tinwelint/2.2-update-puller-inactivity

Correctly responds to inactive update puller
Add query logging.

Three new options added
- log_queries, if true log queries, defaults to false
- log_queries_filename, the file where queries are logged, defaults to `queries.log`
- log_queries_threshold, only log queries that run slower than threshold (in milliseconds)
  defaults to 0, i.e. log all queries.

 This is an enterprise feature.