Is your feature request related to a problem? Please describe.

We have run into issues where less experienced developers have not added scopes properly to their graph objects. This poses a security risk, and we are looking for a way to stop them from pushing insecure object types to our federated graph.

Describe the solution you'd like

I'd like to be able to run a schema validation check and have it fail if a subgraph is trying to push a change which includes a type that doesn't have the @requiresScopes directive applied.

Describe alternatives you've considered

Other options we've discussed are manual reviews of schema changes, but then our team becomes a bottleneck to all other teams pushing graph changes.

Additional context

This is a similar request as #2284 just with a different directive and scope