fix: use thread-safe LogCodedWarning in Aapt2Compile.ProcessDirectory

[Copilot]

Aapt2Compile.ProcessDirectory runs on background threads (via WhenAllWithLock) but logged a warning through the obsolete Log property, which is not thread-safe and can hang Visual Studio. AsyncTask exposes thread-safe logging helpers specifically for this reason.

Change

Replace Log.LogCodedWarning with the AsyncTask thread-safe helper LogCodedWarning — same signature, safe to call from background threads:

// Before
Log.LogCodedWarning ("XA4323", Properties.Resources.XA4323, fileOrDirectory);

// After
LogCodedWarning ("XA4323", Properties.Resources.XA4323, fileOrDirectory);

No behavior change — XA4323 code and message are preserved.

• Fixes [fix-finder] Aapt2Compile: use thread-safe LogCodedWarning instead of obsolete Log property #12291

[Copilot]

Pull request overview

This PR updates the Aapt2Compile MSBuild task to use AsyncTask’s thread-safe warning logging helper when running work in parallel, avoiding the obsolete Log property which can hang Visual Studio when called from background threads.

Changes:

• Replaced Log.LogCodedWarning(...) with LogCodedWarning(...) inside Aapt2Compile.ProcessDirectory.
• Preserved the existing warning code (XA4323) and localized message (Properties.Resources.XA4323) to avoid behavior changes.