Add a maxRefreshInterval option for the pooled jcr sessions

When we have a maxRefreshInterval configurable, we can avoid having jcr sessions accumulating virtual states without ever being refreshed, implying possibly very large memory consumption.

Having a maxRefreshInterval partially avoids this, and makes the session pool less memory consuming, certainly during the times that there are made no changes in the repository