feat: provenance to model to doc

[blanchco]

Description

• A working-ish version of adding and reading provenance for model/dataset enrichments. Will need to do some updates when changes have been made to the data-service around provenance to add document assets. For now I used the EXTRACTED_FROM relation and PUBLICATION for the linking. I'm assuming a relation like ENRICHED_FROM and asset type DOCUMENT will be added in some time.
• provenance linkage happens on profile-model and profile-dataset calls in the backend
• added provenance service to FE
• fixed up getRelatedArtifacts function to retrieve artifacts

Screen.Recording.2023-10-13.at.5.39.22.PM.mov

Resolves #(issue)

[blanchco]

@YohannParis Unsure if we should merge this now or after the provenance updates...
There are some changes needed in provenance like an updated relation type such as ENRICHED_FROM and the DOCUMENT asset type. The provenance linking works albeit the relation and asset type being incorrect. We would simply need to make a few changes in a separate issue update it once the provenance work is updated if we wanted to merge this now.

Also some food for thought, the actual creation of the provenance link might be better done on the knowledge-middleware side for the enrichment jobs. Right now it is adding the provenance link whether or not the job fails or succeeds on the profile-dataset or profile-model calls in the hmi-server. If we were to add the linking on the hmi-client after the enrichment is done there may be cases where the user exits the application in the middle of enrichment and the provenance creation would not happen despite the job being kicked off. So creation of the provenance link on the hmi-server or hmi-client would not be 100%.

cc. @brandomr