.Net: Create a classifiable Kernel Function logger

[feiyun0112]

fix #5989

[stephentoub]

1. This means that the implementation detail of the internal derived type's name will end up showing up in logging. That name could easily change. Is this desirable?
2. We don't need to allocate a new string on each invocation. It can be cached once and then used on each access. That also avoids the duplication between InvokeAsync and InvokeStreamingAsync.

[dmytrostruk]

1. This means that the implementation detail of the internal derived type's name will end up showing up in logging. That name could easily change. Is this desirable?

I think we want to avoid creating logger with name based on function name, because in this case the number of different loggers created will be equal to number of different functions users execute.

Having Microsoft.SemanticKernel.KernelFunction logger name and specific logs like this._logger.LogInformation("Start function execution: {PluginName}-{FunctionName}", this.PluginName, this.Name"); should be enough, and it will be possible to filter logs by FunctionName property in monitoring tool.