repo: lint for correct tracing of errors?

[chris-oo]

Have a lint that fires in the following case:

                        tracelimit::error_ratelimited!(?err, ?offer_id, "could not open channel",);
                        tracelimit::error_ratelimited!(err = err.as_ref() as &dyn std::error::Error, ?offer_id, "could not open channel",);

we want to always require the 2nd, as the first doesn't log the whole error chain.

Originally posted by @SvenGroot in #717 (comment)

[smalis-msft]

Is there a change we could make to tracing instead to do the right thing here somehow? Currently all our lints are purely text-based, and there's no way to have enough type-information to be able to do this. We'd need to invest in setting up something much more involved, like cargo-dylint.