fix(ui) Fix merging siblings schema with mix of v1 & v2 fields

[chriscollins3456]

We had a bug when merging schemas between entities where there was a mix of v1 and v2 schema field names - they wouldn't match as keys so the field would show up twice. Now, normalize these keys so we can merge properly by downgrading everything.

Checklist

• [ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• [ ] Links to related issues (if applicable)
• [ ] Tests for the changes have been added/updated (if applicable)
• [ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• [ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub