It's problematic for ResourceAccessManagerWrapper/CatalogFilterAccessManager.  If the wrapped manager can return null, then the wrapper has nothing to work with and can only return null itself. It's going to lead to most of the performance problems whether it returns null or a bad filter, but there should be a possibility for some small gains if at least some of the filter can be made well known.

So some code simplification (at least the patch would need to make less of a change) vs a possibility of a small performance improvement in large JDBC catalogs.

The whole building the WrapperPolicy thing was already part of the process before, I simply moved it here instead of doing it in SecureCatalogImpl.