Add structured logging to ImageBuilder

Adding structured logging to ImageBuilder would allow us to analyze log outputs and operate on log data using jq or other tools.

I propose that we split ImageBuilder's logging into two components:

• High-level console logging that is concise (fits on ~one terminal screen) and easily parsable by humans and LLMs.
• Detailed structured logging in json that is output to a file and published as a pipeline artifact. One log per ImageBuilder invocation. Put each log file into one folder and upload one log artifact per pipeline job.

Microsoft.Extensions.Logging does not have file logging support natively. See https://github.com/dotnet/runtime/issues/59322. There are a couple libraries that can provide this functionality through M.E.Logging.Abstractions (using ILogger) - both are popular and in active development:

• Serilog (~2B downloads)
• NLog (~500M downloads)

NLog version 6 fully supports Native AOT/trimming so I lean towards that one.

Beginne damit, den ImageBuilder-Einstiegspunkt zu finden und die aktuelle Verwendung von Microsoft.Extensions.Logging zu überprüfen. Untersuche anschließend, wie Pipeline-Jobs Artefakte veröffentlichen, und vergleiche die vorgeschlagenen Ansätze mit Serilog und NLog. Erledigt ist die Aufgabe, wenn eine prägnante Konsolenausgabe, ein strukturiertes JSON-Log pro Aufruf und ein hochgeladenes Log-Artefakt pro Pipeline-Job vorhanden sind.