[Bug] Misspelled "syncronized" in S3 sync response messages

[parthdagia05]

Linked issue

• Closes [Bug] Misspelled "syncronized" in S3 sync response messages #440
• Related: none

Existing related work reviewed

• Issues/PRs reviewed: [Tracking] Minor UI Polish Follow-ups #425 (UI polish tracking — covers frontend typos, not backend response strings), PR fix: correct spelling errors in UI text #374 (DataFile.js/AddCase.js typos — different files entirely), [Task] Remove dead commented-out code and deprecated API route #221 (dead code removal — covers the commented-out instance at CaseRoute.py:528).

Overlap assessment

• Classification: New, non-overlapping fix
• Overlapping items: None
• Why this is not duplicate/superseded: No existing issue or PR addresses the backend "syncronized" typo. The commented-out instance at CaseRoute.py:528 is dead code and intentionally left for [Task] Remove dead commented-out code and deprecated API route #221.

Why this PR should proceed

• 2-line fix in 2 files. User-facing text correction. Zero behavior change. Neither file is upstream-overlap surface per docs/UPSTREAM_SYNC.md.

Summary

• What changed: Corrected "syncronized" → "synchronized" in S3 sync success messages in CaseRoute.py and SyncS3Route.py.
• Why: Misspelled word displayed to users after S3 sync operations.

Validation

• Tests added/updated (or not applicable) — N/A: text-only change.
• Validation steps documented
• Evidence attached

python -m py_compile passes on both files. git diff --check clean. Branched off latest upstream/main (5f8f89a).

Documentation

• Docs updated in this PR (or not applicable) — N/A
• Any setup/workflow changes reflected in repo docs — N/A

Scope check

• No unrelated refactors
• Implemented from a feature branch (fix/typo-syncronized-response-messages)
• Change is deliverable without upstream OSeMOSYS/MUIO dependency
• Base repo/branch is EAPD-DRB/MUIOGO:main

Exception rationale

N/A

[parthdagia05]

@SeaCelo two line typo fix in user-facing S3 sync messages.