Restore missing translations from master to localization branch

[raujaiswal]

Context

#AB2337462

Solving Problem 1 mentioned in the wiki: https://dev.azure.com/mseng/AzureDevOps/_wiki/wikis/AzureDevOps.wiki/51357/Issue-in-Task-repo-Localization-PR

Issue identified from PR: #21459

Problem:

A synchronization issue occurred between the master and localization branches, resulting in translation inconsistencies. The root cause appears to be:

Initial State: Translations for certain variables existed in the master branch but were missing from the localization branch

Likely Cause: A PR containing these translations was merged to master, but the corresponding changes were not merged to the localization branch

Localization Pipeline Run: When the localization pipeline executed, it updated the localization branch with recent .lcl files

PR Creation: The localization branch then raised a PR to master

Resulting Issue: The PR attempted to replace existing translations in master with English versions from the localization branch, because:

• The localization branch contained only English text for these variables
• Master branch already had the proper translations
• The merge attempted to overwrite translations with English source text

Impact: This creates a regression where properly translated content would be replaced with untranslated English text if the PR were merged.

Root Cause: Lack of synchronization between master and localization branch before the localization pipeline runs, leading to the localization branch being out of sync with translation work already completed in master.

Solution:

Identified Inconsistencies: Reviewed the PR #21459 raised from the localization branch and identified translation inconsistencies where English source text was replacing existing translations in master

Retrieved Correct Translations: Extracted the proper translated content from the master branch for all affected resource files

Updated Localization Branch: Applied the correct translations from master to the localization branch, ensuring translated content is preserved

---

Task Name

ANTV1
AzureAppServiceSettingsV1
AzureFunctionAppV1
AzureIoTEdgeV2
BashV3
CacheBetaV0
CacheBetaV1
CacheV2
CopyFilesV2
DecryptFileV1
DeleteFilesV1
DotNetCoreInstallerV0
DownloadGitHubNugetPackageV1
GitHubReleaseV0
GradleV2
GradleV3
InstallAppleCertificateV2
MavenV2
MavenV3
NuGetInstallerV0
NuGetPackagerV0
NuGetPublisherV0
PublishCodeCoverageResultsV2
PythonScriptV0
RunJMeterLoadTestV1
ServiceFabricComposeDeployV0
ServiceFabricUpdateManifestsV2
XamarinAndroidV1

Description

Summarize the changes made in this PR clearly and concisely.

---

Risk Assessment (Low / Medium / High)

Assess the level of risk and provide reasoning (e.g., scope, impact, backward compatibility).

---

Change Behind Feature Flag (Yes / No)

Can this change be behine feature flag, if not why?

---

Tech Design / Approach

• Design has been written and reviewed.
• Any architectural decisions, trade-offs, and alternatives are captured.

---

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

• User guides, API specs, system diagrams, or runbooks are updated.

---

Unit Tests Added or Updated (Yes / No)

Indicate whether unit tests were added or modified to reflect these changes.

---

Additional Testing Performed

List all other tests performed (manual or automated, including integration, regression, scenario tests, etc.).

---

Logging Added/Updated (Yes/No)

• Appropriate log statements are added with meaningful messages.
• Logging does not expose sensitive data.
• Log levels are used correctly (e.g., info, warn, error).

---

Telemetry Added/Updated (Yes/No)

• Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
• Events are tagged with proper metadata for filtering and analysis.
• Telemetry is validated in staging or test environments.

---

Rollback Scenario and Process (Yes/No)

• Rollback plan is documented.

---

Dependency Impact Assessed and Regression Tested (Yes/No)

• All impacted internal modules, APIs, services, and third-party libraries are analyzed.
• Results are reviewed and confirmed to not break existing functionality.

---

Checklist

• Related issue linked (if applicable)
• Task version was bumped — see versioning guide
• Verified the task behaves as expected