Detect directive argument changes

[JoviDeCroock]

Resolves #4237

This mirrors the fields/input-object argument logic but specifically for directives.

[netlify]

✅ Deploy Preview for compassionate-pike-271cb3 ready!

Name	Link
🔨 Latest commit	756f929
🔍 Latest deploy log	https://app.netlify.com/sites/compassionate-pike-271cb3/deploys/6724d0804aa2740008e655ff
😎 Deploy Preview	https://deploy-preview-4277--compassionate-pike-271cb3.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

Hi @JoviDeCroock, I'm @github-actions bot happy to help you with this PR 👋

Supported commands

Please post this commands in separate comments and only one per comment:

• @github-actions run-benchmark - Run benchmark comparing base and merge commits for this PR
• @github-actions publish-pr-on-npm - Build package from this PR and publish it on NPM

[yaacovCR]

Questions:

1. Directive arg change logic matches field arg change logic with respect to safe/dangerous/breaking if the directives are used in operations. Is that always true with respect to directives used to annotate schemas written in SDL?

2. Not directly related to this PR, but => default argument removal seems to marked as dangerous, but it could be breaking if the argument is non-null (because it makes the argument Required from the operation perspective). This fact is not specific to directives, it's true for fields also, but I couldn't find the logic where this was handled for either directives or fields. Is this a separate bug?

[JoviDeCroock]

1. we also don't make the distinction between schema and document directives in the directive removed, we outright flag it as breaking. If we want to change that logic, we should also change it for removal of directives.

2. yes, separate issue