Currently, the Deprecation Info API can only check for conditions that it can detect via the Info or Stats APIs. This leaves us in a position of being unable to detect even some issues that ought to be statically detectable (i.e. not related to reqest/response or API changes). See #36190 for an example of this.

Going forward, we should enable the Deprecation Info API (or add a new API) to read the deprecation logs to allow us to surface issues that aren't detectable via the current implementation, including both issues like the above and usage of deprecated APIs or request formats that will require application changes.