Renaming conflicting resources

[MichalPavlik]

Fixes first part of #11494

Context

We have resources with same name but different content in different projects. It prevents merging our resources to single project and proceed with #11494.

Changes Made

A prefix was added to the resource names to avoid conflicts.

Testing

Existing unit tests.

Notes

This is a minimal change to keep existing behavior.

Copilot reviewed 15 out of 15 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (3)

src/MSBuild/XMake.cs:1312

• Please ensure that the new resource key 'XMake.ProjectUpgradeNeededToVcxProj' is correctly defined in the resource files and that any test expectations relying on the old key are updated accordingly.

InitializationException.Throw(ResourceUtilities.FormatResourceStringStripCodeAndKeyword("XMake.ProjectUpgradeNeededToVcxProj", projectFile), null);

src/MSBuild/XMake.cs:4417

• Confirm that the updated resource key 'XMake.LoggerNotFoundError' is uniformly applied and available across the codebase, as replacing the key may affect logger lookup messages.

InitializationException.VerifyThrow(logger != null, "XMake.LoggerNotFoundError", unquotedParameter);

src/MSBuild/XMake.cs:4421

• Verify that the new resource key 'XMake.LoggerCreationError' is defined in the resource files, and note that similar changes in subsequent catch blocks (lines 4425, 4429, 4433, 4437) should be checked for consistent resource key availability.

InitializationException.Throw("XMake.LoggerCreationError", unquotedParameter, e, false);

[AR-May]

LGTM