Align Dataset fields between provenance_schema.yaml and entity-api-spec.yaml

[kburke]

The fields below are differences noted while cleaning up the Smart API error for entity-api in the Dataset and Dataset:properties. Based on the purpose of each file, align anything necessary.

Stuff in entity-api-spec.yaml "Datasets" but not
provenance_schema.yaml "Datasets":

creators
intended_dataset_type
intended_organ
next_revision_uuids
previous_revision_uuids

Stuff in provenance_schema.yaml "Datasets" but not entity-api-spec.yaml "Datasets":

assigned_to_group_name
dataset_info
dataset_type
direct_ancestor_uuids
ingest_id
ingest_task
lab_dataset_id
new_associated_multi_assay_uuid
pipeline_message
provider_info
run_id
status_history
superseded_associated_processed_component_uuids

[yuanzhou]

@kburke Here are some clarifications:

• creators has been deprecated and replaced with contributors. This applies to all entity types except Upload.
• intended_dataset_type and intended_organ are two properties only for Upload.
• next_revision_uuids and previous_revision_uuids were added originally during the multi-revision work but later we removed them.

The properties that are defined in the schema yaml but not found in OpenAPI/SmartAPI yaml should be added. And we should also generate a new version of SDK to reflect these updates.

• Add assigned_to_group_name, ingest_task, and status_history to both Dataset and Upload
• Add other missing fields only to Dataset