Fix performance issues with many offline sessions - #15463

Thanks for the PR. I have been thinking about this a bit and here are my thoughts:
Should we be worried about reintroducing IN-clause which was removed in last performance optimization attempt? If the userSessionsIds set used in IN-cause gets too big, performance will be probably bad. However, I think we should be OK because userSessionIds size should be reasonable. There are these use-cases:

• load user session by user (not limited by first,max parameters as it is called with first=0, max=null, but limited by number of user session which user can has. Not sure if this can be a high number in real scenarios. Maybe yes, if someone creates many offline user sessions for a user by i.e password grant type)
• load user sessions by client (this can be a high number but it is called only from services and endpoint is limiting max result size -- 100 by default)
• load user sessions by interval - IN clause not used and method is called only from pre-loading

@hmlnarik What are your thoughts on this?

@hmlnarik What are your thoughts on this?

Thank you for the reply. These are exactly the arguments why I am in favour of introducing the IN clauses for the cases when the session is known in advance while keeping the interval for preloading, and this PR should reflect it.