Un-deprecate Location based Content criteria that works as intended

The orginal reason (applying to random content locations, see #701)
why this was deprecated does not apply to criteria that actually
filters on specific locations.

When it comes to visibility this is such a common use case
that it is rather documented that it will include content
if it has *any* location that is hidden or visible. We may
consider to add flag or changing default behavour so it
always check all locations. But current behavoiur has several use
cases as well, at least from permission perspective if visibility
becomes part of it. For other use cases use LocationSerach.