Improve logging using structured logs

[MattMcL4475]

Problem:
Logs contain log messages which don't uniformly refer to identifiers (like the TES task ID). This makes it difficult and/or impossible to trace the life cycle of a TES task through the system.

Solution:
Instead of:

string msg = $"TES task: {tesTask.Id} BatchTaskState: {combinedBatchTaskInfo.BatchTaskState}";
logger.LogInformation(msg);

Can do something like this:
logger.LogInformation("TES task: {tesTask.Id} BatchTaskState: {combinedBatchTaskInfo.BatchTaskState}", tesTask.Id, combinedBatchTaskInfo.BatchTaskState);

This issue is to comprehensively design a better way to improve logging so that it's easier to debug the lifecycle of a TES task and see any Batch issues that may be related to it, as well as easily query it in Application Insights traces. The solution should include clear examples of how to query in Application Insights traces.

[ngambani]

@MattMcL4475 do we have any update on this one. Is this something we want to work on or has already been addressed?