Improve tracing for missing converters

From the investigation in https://github.com/Azure/azure-functions-dotnet-worker/issues/1141, it was discovered that there was no converter supporting the specific parameter type and there were no logs along this path that would notify users about an unhandled conversion.

For future scenarios, we want to improve tracing to help root cause these issues more efficiently.

Start by reviewing the investigation in issue #1141 and tracing the missing-converter path described there. Determine where an unsupported parameter conversion becomes unhandled, then add tracing that clearly identifies the conversion failure and verify the resulting logs.

Written by the indexing model from the issue text.