Use structured logging in logs instead of string interpolation

[Arithmomaniac]

Two related points:

• For clarity and compatability, logs should use the new log syntax, e.g. LogDebug; the old methods are just legacy compatabiltiy shims (see Legacy LogConsumer provider sink for Microsoft.Extensions.Logging dotnet/orleans#3284).
• Use placeholders instead of string interpolation. From https://blog.rsuter.com/logging-with-ilogger-recommendations-and-best-practices/:

To ensure that a message template is correctly logged and properties are transferred as custom properties, you always need to log properties with placeholders in the correct order, e.g.
logger.LogWarning("The person {PersonId} could not be found.", personId);
Never use string interpolation because the replacement will be done in your application and the logging backend has no longer access to the message template and individual custom properties:
logger.LogWarning($"The person {personId} could not be found.");
Another downside of string interpolation is that objects are always serialized into text in your app even if the log is not actually written because there is a log level filter configured.

Together, this would turn

Orleans.Sagas/Orleans.Sagas/SagaGrain.cs

Line 224 in 8796433

logger.Debug($"Executing activity #{State.NumCompletedActivities} '{currentActivity.GetType().Name}'...");

into something like
logger.LogDebug($"Executing activity #{activityNumber} '{currentActivityName}'...", State.NumCompletedActivities, currentActivity.GetType().Name)