Improve UX for handling conflicts when importing metadata schemas

[kburger]

What is your question?

When I try to import a metadata schema from another FDP and there are conflicts, the UI currently shows a red Conflict badge and prevents the importing of shapes. The only option a user is given is to show the shape contents, but that leaves the figuring out of how, where, or why there are conflicts to the user.

Maybe a diff visualization, or a short summary on which attributes or properties are conflicting would be helpful in guiding the user to solve the conflicts.

[KarolisCremers]

Just a comment on this:
My current workaround is to copy the shacl and manually try to add the shape through the metadata-schema's interface and trying to "save and release" it. This sometimes provides error message, or just works.