Consider ILog method overloads to accept a MethodInfo instance

[sbohlen]

When logging is invoked from e.g., aspects/advice, Common.Logging reports the callsite of the log message as being in the aspect/advice rather than in the 'target' of the advice. While this is technically accurate/correct, its likely not what the reader of a log message really wants to see as the origin of the log message.

We should consider extending the ILog interface to offer overloads that accept an explicit MethodInfo or sim. parameter so that logging code can explicitly provide the callsite context which it would prefer Common.Logging to record as the 'logical' location of the source of the log message.