Extend support for @deprecated directive

[wimski]

The @deprecated directive currently is only allowed on FIELD_DEFINITION and ENUM_VALUE:

"""
Marks an element of a GraphQL schema as no longer supported.
"""
directive @deprecated(
  """
  Explains why this element was deprecated, usually also including a
  suggestion for how to access supported similar data. Formatted
  in [Markdown](https://daringfireball.net/projects/markdown/).
  """
  reason: String = "No longer supported"
) on FIELD_DEFINITION | ENUM_VALUE

However any schema element could become deprecated at some point, like an obsolete/unused input field for example. Would it be possible to add the following to the supported types of the @deprecated directive?

• ARGUMENT_DEFINITION
• INPUT_FIELD_DEFINITION

[spawnia]

Looks like this will be possible in an upcoming version of the GraphQL specification - see graphql/graphql-spec#805 (comment)

We have to implement this in the base library first though, see webonyx/graphql-php#110

[owenvoke]

@spawnia, is this now ok to implement for Lighthouse? 👀

[spawnia]

It is already possible to use @deprecated as described, given https://github.com/webonyx/graphql-php/releases/tag/v15.4.0 is installed. I updated our definition of the directive in #2607.

[spawnia]

Released the updated definition with https://github.com/nuwave/lighthouse/releases/tag/v6.44.0.

[owenvoke]

@spawnia, interestingly, when dumping the schema with php artisan lighthouse:print-schema, it strips the @deprecated tag from the output for both of these. When looking into it, it seems like the deprecationReason property never gets added for arguments.

I've opened #2609 to fix the issue, but please let me know if I'm missing something.