Update the CodeSystem provenance with AIAST decoration and it fails

[JohnMoehrke]

A CodeSystem Provenance is handled by the IG Publisher to show the provenance history of a codeSystem. But when I also make that Provenance compatible with the AIAST profiling then that IG Publisher showing CS provenances stops. Will work with Grahame to allow this to work properly.

[JohnMoehrke]

DO NOT MERGE

[JohnMoehrke]

CodeSystem Provenance handling seems to be too strict? I added a CS provenance to the AI-Transparency IG, and it shows. But when I update that Provenance with AIProvenance profiling, the whole Provenance is ignored thus no longer showing CS provenance. I suspect the CS provenance handling is being a bit too strict, wanting only one provenance.reason that is exactly #METAMGT?

https://build.fhir.org/ig/HL7/aitransparency-ig/branches/moehrke-combined-cs-ai-provenance/CodeSystem-AIdeviceTypeCS.html

https://build.fhir.org/ig/HL7/aitransparency-ig/branches/moehrke-combined-cs-ai-provenance/Provenance-AIdeviceTypeCS-initial-history.html

[JohnMoehrke]

The change critical to showing history or not showing history is if the Provenance is profiled or not. If it is profiled then the history table will not show.

InstanceOf: Provenance
vs
InstanceOf: AIProvenance

A diff on the fsh-generated folder shows that the only difference is that the second will have a .meta.profile element.

Suspected this was related to Usage of #definition vs #example; but this is always set to #definition and sushi never marks the output as example.