top-level DataProcessing would require a different uniqueness level for data_processing_id

[schristley]

The current DataProcessing object is a sub-object within Repertoire so it's data_processing_id only needs to be unique within a repertoire. If we want to make DataProcessing a top-level object, or at least generalize it beyond Repertoire so that it can describe operations on RepertoireSet, Clone and etc., then it's uniqueness level should change so that the id can be used across multiple objects.