Do not consolidate changes for Parent Entities

[harshach]

Feature
In OpenMetadata, we capture every change to a data asset and version it. This provides a great view for users, owners and data goverance teams to understand the evolution of a data asset , including who changed and when. This change event also triggers a thread for conversations.
We introduced a consolidation of entity versioning if the change happens with-in 10mins by the same user against the same data asset. This provides a way to reduce unnecessary noise and reduced the no.of versions an asset goes through.
However this puts an issue when a parent entity change is consolidated. Whenever there is a change to a data asset, we generate a change event which used to propagate changes to children entities. For example a change to classification to disable should disable all of its children tags in search index.
However if the enable/disable happens with-in a session time by the same user only the first change is applied not the second change because of consolidation.

In this ticket, we will not apply change consolidation to parent entities.

Parent entities less likely to change unlike their children, example database metadata is less likely change compared to Table.
So this exception for Parent entities should be ok in not having huge affect in entity versions.