Fix trx in case of exit code != 0

[MarcoRossignoli]

This pull request introduces changes to the TrxReportGenerator and related classes to include the process exit code in the TRX report generation. The most important changes include adding a new dependency for ITestApplicationProcessExitCode, updating the TrxReportEngine to handle the exit code, and modifying the result summary to reflect the exit code.

Changes to TrxReportGenerator and Dependencies:

• src/Platform/Microsoft.Testing.Extensions.TrxReport/TrxDataConsumer.cs: Added ITestApplicationProcessExitCode as a dependency and updated the constructor and OnTestSessionFinishingAsync method to use it. [1] [2] [3] [4]

Changes to TrxReportEngine:

• src/Platform/Microsoft.Testing.Extensions.TrxReport/TrxReportEngine.cs: Added _exitCode field and updated the constructor and methods to handle the exit code, including modifying the GenerateReportAsync and AddResultSummaryAsync methods to use the exit code. [1] [2] [3] [4] [5] [6]

Changes to TrxProcessLifetimeHandler:

• src/Platform/Microsoft.Testing.Extensions.TrxReport/TrxProcessLifetimeHandler.cs: Updated methods to include the exit code when publishing messages. [1] [2]

Additional Changes:

• src/Platform/Microsoft.Testing.Extensions.TrxReport/TrxReportExtensions.cs: Updated to include ITestApplicationProcessExitCode in the service provider.
• src/Platform/Microsoft.Testing.Platform/Hosts/ConsoleTestHost.cs: Changed to use synchronous GetProcessExitCode method.
• src/Platform/Microsoft.Testing.Platform/Hosts/TestHostBuilder.cs: Added and set up TestApplicationResultProxy to manage the exit code service. [1] [2]

Localization Updates:

• Added new localized string for "The ITestApplicationResult has not been built yet." in multiple resource files. [1] [2] [3] [4] [5] [6]

fixes #3768