JCRSessionStatefulConcurrencyValve can incorrectly assume a session stateful jcr LazySession

When a hst:mount is marked to be

<sv:property sv:name="hst:sessionstateful" sv:type="Boolean">
<sv:value>true</sv:value>
</sv:property>
<sv:property sv:name="hst:subjectbasedsession" sv:type="Boolean">
<sv:value>true</sv:value>
</sv:property>

this doesn't necessarily imply a LazySession as the resolved mount or sitemapitem might not have hst:authenticated = true at all.

Hence, incorrectly, the session gets refreshed on every request.