Consider reducing the criticality of adding new union members?

[martinbonnin]

graphql-inspector currently considers adding new members to an union as Dangerous.

While this could break some clients, I believe there are ways to guard against this on the client side and adding new union members is an important tool for schema evolution that we should encourage as a community.

What about introducing a new less scary ADVISORY criticality level?

export enum CriticalityLevel {
  NonBreaking = 'NON_BREAKING',
  Advisory = 'ADVISORY',
  Dangerous = 'DANGEROUS',
  Breaking = 'BREAKING',
}

This, coupled with best practices how to handle unkown types/enum values on the client, would allow teams to update their schemas much more confidently.

Thoughts?