update registry-manager load-data to handle additional use cases

[rchenatjpl]

registry-manager load-data balks at three different places in the .xml, all marked with "RC" in comments. This one might be a bug:
<lidvid_reference>urn:nasa:pds:context:investigation:mission.orex::1.0</lidvid_reference>
<reference_type>data_to_investigation</reference_type>
This one Eugene has previously suggested loading my own data dictionary, I think
<lid_reference>urn:nasa:pds:context:facility:observatory.dsn</lid_reference>
<reference_type>is_facility</reference_type>
This might be the same
<Reference_List>
<Internal_Reference>
<lid_reference>urn:nasa:pds:orex.dsndsn:trk234_trknav</lid_reference>
<reference_type>ancillary_to_data</reference_type>
The calibration data products are documented in:
</Internal_Reference>
</Reference_List>

The last two are pretty common, so I suggest the default for registry-manager be to accept them. The first one - when I review stuff, I discourage people from making lidvid_references, but it does happen, and it's legal.

regapp10.zip

[jordanpadams]

@tdddblog @tloubrieu-jpl can we take a look at getting this update in before we do a new release of registry-app?