Don't flag dangerous changes on 0-usage types #7608
Description
Right now if you make a dangerous change (e.g. adding an enum value) to a type with 0 usage, validation for dangerous changes will fail. It should instead be marked safe based on usage.
{{ message }}