`slot_usage` parent issue

[turbomam]

• never assert multivalued in a slot_usage
• never assert inlined* in a slot_usage
• only use a range slot_usage to change the range to a more specific subclass of whatever is declared in the global slot definition.

[turbomam]

see

• https://github.com/microbiomedata/nmdc-schema/issues/1892
• https://github.com/microbiomedata/nmdc-schema/issues/1830
• https://github.com/microbiomedata/nmdc-schema/issues/1587 [CLOSED VIA BERKELEY]
• https://github.com/microbiomedata/nmdc-schema/issues/1547 [CLOSED VIA BERKELEY]
• https://github.com/microbiomedata/nmdc-schema/issues/1498
• https://github.com/microbiomedata/nmdc-schema/issues/1467

[turbomam]

Some of these are confusions about what should be expressed in the nmdc-schema and what should be handled in the submission portal

Problems (in berkeley-schema-fy24):

see

• https://github.com/microbiomedata/nmdc-schema/issues/1901

Redundant

see

• 1900

OK

• CollectingBiosamplesFromSite.slot_usage.has_input.range: NamedThing -> Site
• CollectingBiosamplesFromSite.slot_usage.has_output.range: NamedThing -> Biosample
• DataGeneration.slot_usage.part_of.range: NamedThing -> DataGeneration
• DataGeneration.slot_usage.has_output.range: NamedThing -> DataObject
• FunctionalAnnotation.slot_usage.was_generated_by.range: WorkflowExecution -> MetagenomeAnnotation
• MaterialProcessing.slot_usage.has_output.range: NamedThing -> ProcessedSample
• MaterialProcessing.slot_usage.has_input.any_of.range: NamedThing -> Biosample or ProcessedSample
• MixingProcess.slot_usage.has_output.range: NamedThing -> ProcessedSample
• SubSamplingProcess.slot_usage.has_output.range: NamedThing -> ProcessedSample