Nate Lust can you please take a look at this.
Because the connections are created in one place and we warn about deprecation in another, I need to calculate where the original deprecation comes from.
The current message is:
finalVisitSummary (from /Users/timj/work/lsstsw/stack/lsst-scipipe-7.0.0/Darwin/pipe_tasks/g85f8d04a89+f020c27613/python/lsst/pipe/tasks/makeWarp.py:121): Deprecated in favor of 'visitSummary'. Will be removed after v26.
Which is now useful and tells you exactly where the connection is being set.
The downside is that the calls to inspect.stack() take some time because we call it for all deprecated connections even if we don't issue the warning message later on. In the drp_pipe tests we only issue a warning for finalVisitSummary and don't warn on the tens of other times where a deprecated connection is used. The drp_pipe tests (single process) change from 19s to 21s. Maybe that's fine for the increased visibility and the fact that most of these deprecations are going away in the next month.
I haven't looked at the deprecatedTemplates deprecation to see how informative that message is.