fix: fix help request validation/save failures during edit

[AlperKartkaya]

What was wrong

• Existing request location values are stored as labels like Turkey, Istanbul, Kadıköy.
• The edit form dropdowns expect selector keys like tr, istanbul, kadikoy.
• So when editing, already-filled location fields could appear empty/unselected.
• I also found a related save-risk: stored phone values like 90555... could hydrate into an invalid phone input instead
  of 555..., causing validation/save failures during edit.

Fixed

Resolves #613

Changed:

• android/app/src/main/java/com/neph/features/requesthelp/presentation/RequestHelpScreen.kt
  • Normalizes persisted help type/risk/vulnerable group values back into UI option labels.
  • Converts persisted location labels back into dropdown keys.
  • Normalizes stored Turkish phone numbers with 90 prefix into editable form values.
  • Waits for location options before hydrating an existing draft/edit form.

Added tests:

• android/app/src/test/java/com/neph/features/requesthelp/presentation/RequestHelpFormStateMappingTest.kt
  • Covers edit-form hydration for persisted labels, dropdown keys, phone normalization, and unknown remote locations.
• android/app/src/androidTest/java/com/neph/e2e/RequestHelpRepositoryAndroidTest.kt
  • Confirms edited request fields are actually persisted in the local database.

[erinc00]

LGTM. This fixes the edit-form hydration issue in the right place by mapping persisted values back into the form shape the UI expects. The location label-to-key conversion and phone normalization should prevent the empty dropdown / invalid phone problems during edit, and the added tests cover the main regression paths. Approving and merging.