Regression since bumping resource-pool from `0.4.0.0` to `0.5.x`

[swamp-agr]

Resource pool while fixing a bug introduced a couple behavioural changes in resource destroying:

• Masking:
  • In 0.4.x it was uninterruptible.
  • Since 0.5.x it has become interruptible.
• exception handling:
  • In 0.4.x it silently ignored all exceptions.
  • Since 0.5.x it has started loudly allowing throwing exceptions.

loggingClose from persistent became no longer safe. It could lead to situations where file descriptor and associated database connection will remain opened while connection declared released by the pool, i.e. leaking fds/sockets. Solution would be to make it explicitly uninterruptible.