Ability to target schema change slack notifications by sub-graph, client, operation or type. Oh my!

[setchy]

To set some context, the federated GraphQL roll-out at my organization is going very well. Every sprint we are adding 1-2 new sub-graph and we are making schema changes all the time 🎉

We have a number of product-specific Slack channels which are currently registered for Schema Change Notifications so that our front-end teams can see updates to the GraphQL Schema. This was working really well for the first few product teams needed.

More recently though, the frequency of notifications is increasing and the relevance of the slack notifications to a particular product channel is decreasing.

It would be great to be able to filter the schema change notification to be either at a variant level (current), sub-graph(s), client(s) or operation(s) level so that we could target the notifications for a given slack channels audience

[kartikkgujarati]

Similar to https://github.com/apollographql/apollo-studio-community/issues/48

[setchy]

Not being able to setup performance notifications at a subgraph level AND prior to clients consuming and naming the operation is starting to introduce developer/adoption friction.