consider moving metalnx-core to jargon-irods-ext

[michael-conway]

The https://github.com/DICE-UNC/jargon-extensions-if project is moving towards a generalized interface that can absorb iRODS best practices for things like stars, shares, metadata templates, etc.

https://github.com/DICE-UNC/jargon-irods-ext is an implementation of the extensions interfaces that can bridge between the cloud browser and metalnx and allow a gradual merging of these concepts,as well as virtual collections, tags, saved queries, file format recognition, preview and thumbnail generation.

This is meant to be a stake in the ground and a way to adapt site-specific implementations of these common concerns that maximizes the applicability of MetaLnx and other interfaces (gui and REST) that are aimed at these sort of commodity functions. This also allows a gradual factoring of things like metadata templates into the iRODS core, via V5 API, etc.

Right now, metalnx is using the data profiler in jargon-irods-ext as the basis for its 'data and collection home page'. The data profiler can give a summary of the characteristics of a file or collection at a path, is it starred? Is it shared? Does it have current tickets?

We're proposing to put the metalnx database code underneath jargon-irods-ext (the metalnx-core subproject) to avoid circular references between metalnx and irods-ext. Thus the data profiler in the default implementation can use the metalnx database for 'stars and favorites' now and migrate towards using iRODS AVUs etc.

So this is an issue to migrate that subproject under jargon-irods-ext and then configure it as a dependency in metalnx.