Analyzer for RequestInformation

Let's pick on one example from https://github.com/microsoftgraph/dotnet-aad-query-sample/blob/main/GraphDataService/GraphDataService.cs

        public IAsyncEnumerable<Group> GetGroups(string[] select, string filter, string[] orderBy, string search)
        {
            var requestInfo = _graphClient.Groups
                    .ToGetRequestInformation(rc =>
                    {
                        rc.Headers = EventualConsistencyHeader;
                        rc.QueryParameters.Count = true;
                        rc.QueryParameters.Select = select;
                        rc.QueryParameters.Filter = filter;
                        rc.QueryParameters.Orderby = orderBy;
                        rc.QueryParameters.Search = search;
                    });

            LastUrl = WebUtility.UrlDecode(requestInfo.URI.AbsoluteUri);
            return requestInfo.ToAsyncEnumerable<Group, GroupCollectionResponse>(_graphClient.RequestAdapter);
        }

Here - obviously - the eventual consistency header is set. However, having a Roslyn analyzer/fix that would tell me if I actually forgot it in a call where it should have been added to RequestInformation would be great (eg the ASP.NET team does ship such best practices or deprecated patterns analyzers).

Start with the RequestInformation usage shown in GraphDataService/GraphDataService.cs and investigate how the .NET SDK represents the eventual consistency header. Define which requests require the header and how a Roslyn analyzer and code fix would identify and address missing usage; done means those patterns are diagnosed reliably with an actionable fix.