a suggestion for the team to consider:
1. better explain the limitations of version history (in UI) to a regular user viewing the changes, because they wont appreciate the purpose nor differences between editableMetadataSchema and MetadataSchema. All they would take away is that they made a change in the UI, but version history doesnt show any change.
2. remove the feature first while version history is reworked to include editableMetadataSchema changes.
3. stop ingesting new versions of SchemaMetaData that has no change (I assume new versions were added because of the auditTimestamp change)