Logs / Metrics for input and output bindings for detectors

From looking at detector's logic for identifying the list of input and output bindings, it seems like it relies on `function.binding.` metric emitted over the previous couple of days. However, this particular metric is not emitted in the following scenarios.

- When a function is never executed.
- Dotnet in-proc scenarios.

We need to have a standard way of knowing the list of bindings and triggers from logs/metrics irrespective of the language and irrespective of whether a function executes or not.

cc: @brettsam