add support for native executable entrypoint in container publishing

[Gérald Barré (geraldbarre-workleap)]

Jira issue link: FENG-1866

Description of changes

Breaking changes

Additional checks

• Updated the documentation of the project to reflect the changes
• Added new tests that cover the code changes

[Copilot]

Pull request overview

This pull request adds support for native executable entrypoints in container publishing for .NET projects. When enabled, containerized applications will use the native executable (e.g., /app/myapp) instead of the default .NET runtime invocation (e.g., dotnet /app/myapp.dll) as the container entrypoint.

Changes:

• Added a new MSBuild property ContainerUseNativeCommand (default: false) to enable native executable entrypoints
• Implemented an MSBuild target that modifies the container entrypoint when publishing single-RID container builds
• Added a test to verify the entrypoint is correctly set when the feature is enabled
• Extended ProjectBuilder test helper with a new ExecuteDotnetCommand method for generic dotnet command execution

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
src/build/Workleap.DotNet.CodingStandards.props	Adds the ContainerUseNativeCommand property with a default value of false
src/build/Workleap.DotNet.CodingStandards.targets	Implements the UpdateContainerCommand target that replaces the container entrypoint with the native executable path for single-RID builds
tests/Workleap.DotNet.CodingStandards.Tests/Helpers/ProjectBuilder.cs	Adds a new ExecuteDotnetCommand method to execute arbitrary dotnet commands and capture output
tests/Workleap.DotNet.CodingStandards.Tests/ContainerTests.cs	New test file with a test that verifies the native executable entrypoint is used when ContainerUseNativeCommand is enabled

Comments suppressed due to low confidence (1)

tests/Workleap.DotNet.CodingStandards.Tests/Helpers/ProjectBuilder.cs:6

• The using statements should be ordered alphabetically. System namespaces should be grouped together and sorted alphabetically, followed by other namespaces sorted alphabetically. The expected order would be:

• using System.Text;
• using System.Text.Json;
• using System.Xml.Linq;
• using CliWrap;
• using Xunit.Abstractions;
• using Xunit.Sdk;

using System.Text;
using System.Xml.Linq;
using Xunit.Abstractions;
using System.Text.Json;
using CliWrap;
using Xunit.Sdk;