And mark a couple to be retired afther the next release branch.
the code looks good to me, but we need to be a bit careful on landing this -- as we have an internal client setting this flag.
our internal client explicitly set this to true, so we need a migration plan for this, otherwise this would break our build of internal client during the integration, a possible plan is
Or just remove the flag internally, then land this patch in upstream (but internal release has to pick-up these two together)
Discussed offline - there's no reason to block for out-of-tree clients here.
(We're removing support for a configuration - SuggestMissingIncludes = false - which is AFAIK unused anywhere. And we're removing the flag as well, but this is a trivial API change to adapt to)