@deprecated directive usage, reason not defaulting of No longer supported as per the spec

[arseniocosta1]

What happened?

If you define a field as @deprecated without providing a reason one would expect the default value set to deprecationReason in the introspected schema to be as per the
spec with a value of No longer supported

What did you expect?

When deprecating a field without specifying a reason the introspection of the schema should set a
deprecationReason of No longer supported
`

type Customer {
  id: UUID!

 
  subscription: SubscriptionDetails! @deprecated
}

Minimal graphql.schema and models to reproduce

versions

• go run github.com/99designs/gqlgen version?

v0.17.33

• go version?

[arseniocosta1]

I submitted #2692 which fixes it, but as I am quite new to the codebase I am not sure if, the fix is applied in the most correct place

Feel free to discard that PR or edit it