Private resource maps should not display as a table in the MetadataView

[laurenwalker]

We should only display tables when the resource map object itself is accessible, even if all or some of the members are public. This causes issues when an obsolescence chain has more than two private rmaps.

Example: mapA isObsoletedBy mapB isObsoletedBy mapC

mapA is public, mapB and mapC are private.

The expectation is that when viewing the MetadataView logged out, only mapA will be shown since mapA is the most recent accessible resource map. But what happens instead is mapB and mapC are both shown. This is because Solr returns the following info:

mapA isObsoletedBy mapB mapB isObsoletedBy null mapC isObsoletedBy null

So MetacatUI retrieves the members of maps B and C, and renders those two tables on the page.

[robyngit]

@rushirajnenuji, tagging you here because this might be a case to test for in your changes to the package table view?