Translatable task title

[FikriMilano]

IMPORTANT: Where possible all PRs must be linked to a Github issue

Fixes #3812

Task descriptions extracted from ActivityDefinition.productCodeableConcept are now translatable using the ConfigurationRegistry translation system. This implementation provides two methods for translating task descriptions with automatic fallback to original text when translations are missing.

• Config rules: @{translate(task.description)}
• Kotlin extension: task.getLocalizedDescription(configurationRegistry)

1. Task.description: "Discuss-Confidentiality"
         ↓
2. Generate key: translationPropertyKey()
         ↓
3. Key: "discuss.confidentiality"
         ↓
4. Lookup in strings_config.properties (or strings_fr.properties, etc.)
         ↓
5. Found? → Return translation
   Not found? → Return original (fallback)
         ↓
6. Output: "Discuss Confidentiality (English)"
       or: "Discuter de la Confidentialité" (French)
       or: "Discuss Confidentiality" (fallback if missing)

Engineer Checklist

• I have written Unit tests for any new feature(s) and edge cases for bug fixes
• I have added any strings visible on UI components to the strings.xml file
• I have updated the CHANGELOG.md file for any notable changes to the codebase
• I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
• I have built and run the FHIRCore app to verify my change fixes the issue and/or does not break the app
• I have checked that this PR does NOT introduce breaking changes that require an update to Content and/or Configs? If it does add a sample here or a link to exactly what changes need to be made to the content.

Code Reviewer Checklist

• I have verified Unit tests have been written for any new feature(s) and edge cases
• I have verified any strings visible on UI components are in the strings.xml file
• I have verifed the CHANGELOG.md file has any notable changes to the codebase
• I have verified the solution has been implemented in a configurable and generic way for reuseable components
• I have built and run the FHIRCore app to verify the change fixes the issue and/or does not break the app

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 24.6%. Comparing base (aaebbb6) to head (5daf4d9).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main   #3814     +/-   ##
=========================================
- Coverage     25.0%   24.6%   -0.5%     
- Complexity     844     849      +5     
=========================================
  Files          297     303      +6     
  Lines        16102   16485    +383     
  Branches      2689    2744     +55     
=========================================
+ Hits          4038    4068     +30     
- Misses       11580   11935    +355     
+ Partials       484     482      -2     

Flag	Coverage Δ
engine	60.9% <100.0%> (-0.1%)	⬇️
geowidget	21.7% <ø> (+3.1%)	⬆️
quest	4.5% <ø> (-0.2%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
...gister/fhircore/engine/rulesengine/RulesFactory.kt	66.9% <100.0%> (+0.3%)	⬆️
...fhircore/engine/util/extension/StringExtensions.kt	75.0% <100.0%> (+3.1%)	⬆️
...er/fhircore/engine/util/extension/TaskExtension.kt	62.8% <100.0%> (+12.8%)	⬆️

... and 7 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.