Follow-up from "Fix GraphQL error for VulnerabilityType"

The following discussion from !121787 (merged) should be addressed:

• @cablett started a discussion: (+1 comment)

  Question: do we have request specs that would have caught this? I'm a little concerned there might be others. Often we use all_graphql_fields_for helper to ensure that any fields like this are noisily caught before being removed 🤔