issues with was_generated_by

[aclum]

• [ ] do we need this slot? It is redundant, creating a bi-directional graph with has_output when it is used on data objects. Class FunctionalAnnotation is not currently being used. If we remove it we shouldn't do this until after re-iding.
  • [ ] If we keep this we need to add OmicsProcessing to the range, both WorkflowExecutionActivity subclasses and OmicsProcessing generate DataObject records which can use this slot
  • [ ] AttributeValue lists was_generated_by as a slot but the range is Activity. Do we need this slot on this class, if so we need to update the range of was_generated_by to be more than Activity. @cmungall @sierra-moxon @turbomam

related to #1846

to do: make example DataObject records where was_generated_by values are from either a WorkflowExecutionActivity subclass or an OmicsProcessing.

[aclum]

Solution for now, remove was_generated_by from AttributeValue, update range using any_of to include OmicsProcessing. In berkeley schema both DataGeneration and WorkflowExecution share a parent of PlannedProcess.