Broader provenance tracking beyond mapping related changes #118
Description
I believe the original intention for the provenance was to capture changes to mappings, however, there are other places where it makes sense to capture changes as users make updates. One place that is currently not being tracked are changes to the users preferences and preferred terminologies.
It seems reasonable to expand our provenance to include all changes being made to these other aspects of the backend data.