HstRequestContext#getSession() returns wrong JCR Session in Wicket code

Since version 13.0.0, CMS wicket code can get hold of the HstRequestContext, simply by

final HstRequestContext requestContext = RequestContextProvider.get();

If however in CMS Wicket code then the JCR Session is requested from the request context, via

final HstRequestContext requestContext = RequestContextProvider.get();
requestContext.getSession();

then the CMS JCR Session should be returned. However, currently, when this is invoked, the HST will return a pooled live user session since the HstRequestContext did not yet have an associated JCR Session. This is likely to result in problems. In Wicket code, the JCR Session from the wicket code should be returned.