User can create a project with an existing name — project is created with "(1)" suffix but not uploaded to the server

Description
When a user creates a new project using a name that already exists in the same workspace, the app does not block the creation. Instead, it silently renames the new project by appending (1) to the name (e.g. my_project becomes my_project(1)). However, the project is never uploaded to the server — the renamed project exists only locally with no corresponding entry on the server.

Environment
Staging

Application (+ app version, build, operating system)
Mergin Maps Mobile App

• Android version: 2025.6.0 — Samsung Galaxy A53 5G, Android 15
• iOS version: 2025.6.0 — iOS 26.0

Steps to reproduce

1. Log in to the Mergin Maps mobile app.
2. Navigate to the Projects list.
3. Note the name of an existing project in the workspace (e.g. my_project).
4. Create a new project using the exact same name (my_project).
5. Complete the project creation wizard and confirm.
6. Observe the project name shown in the app and check the server (web dashboard).

Actual results
The project creation wizard completes without any error or validation warning. The new project is created locally with (1) appended to the name (e.g. my_project(1)). The project is not uploaded to the server — no entry for my_project(1) (or my_project) appears on the server.

Expected results
Either:

• The app should prevent the user from completing the creation wizard and display a clear validation error: "A project with this name already exists. Please choose a different name."
• Or, if the (1) suffix renaming is intentional behaviour, the renamed project (my_project(1)) should still be uploaded to the server successfully, and the user should be informed about the name change.

Screenshots or logs

https://github.com/user-attachments/assets/ae91b8c6-aa9e-424a-b0d3-0c53ab9ebe68

No source file or test is named; start by reproducing the duplicate-name flow in the Mergin Maps mobile app on the listed Android or iOS versions, then trace project creation through the server upload check. Done means the chosen duplicate-name behavior is explicit, the project is handled consistently, and the result is verified in the web dashboard.