add more information on union fields being removed (#2838)

* add more information on union fields being removed

* update wording

* updated wording

* add minor bump and changeset

---------

Co-authored-by: Emily Goodwin <[email protected]>

Author: egoodwinx

.changeset/lazy-lemons-vanish.md

@@ -0,0 +1,6 @@
+---
+'@graphql-inspector/core': minor
+---
+
+Updated removing field message to contain more information on why its a breaking change such as if
+the field is a union or indirectly referenced.

packages/core/src/diff/changes/field.ts

@@ -39,7 +39,7 @@ export function fieldRemovedFromMeta(args: FieldRemovedChange) {
       level: CriticalityLevel.Breaking,
       reason: args.meta.isRemovedFieldDeprecated
         ? `Removing a deprecated field is a breaking change. Before removing it, you may want to look at the field's usage to see the impact of removing the field.`
-        : `Removing a field is a breaking change. It is preferable to deprecate the field before removing it.`,
+        : `Removing a field is a breaking change. It is preferable to deprecate the field before removing it. This applies to removed union fields as well, since removal breaks client operations that contain fragments that reference the removed type through direct (... on RemovedType) or indirect means such as __typename in the consumers.`,
     },
     message: buildFieldRemovedMessage(args.meta),
     meta: args.meta,