structured data in some cases fails to be created after upload

[nylki]

Sometimes a file gets succesfully uploaded and is published and visible, however the structured data was not created. This occasionally happens, but I haven't seen a reliable cause of the reason and hard to repro.

[nylki]

This can currently happen in cases where the upload and the un-stashing was succesful, but got interrupted just after the un-stashing network request. This may be caused by:

• A: network issues
• B: user closes the app too soon or puts it into background when the progress-bar is filled (but network requests are still being done)
• C: less likely, some other network error due to malformed HTTP data or API changes, etc.

B should be less of a issue in iOS26 where the BGContinuedProcessingTask will make sure to continue the publishing task; unless the user hard-closes the app (swiping up in app chooser)

What amplifies the UX-problem when this occurs, that the user can start the upload again, because the draft is still there. However the filename will now conflict, because it already exists from the previous upload.

So to make this more clear to the user what happens, I think the following changes would be useful:

• the upload state should stored in the Draft item in the DB
• drafts that have have a started upload should pick up from their previous step (ie: if last succesful step is .unstashingFile or .creatingWikidataClaims, we can assume that step didn't finish, and prompt the user to retry)
• on app-start: fetched uploaded files from network (already done) and check if one of their filename matches any Draft that has .creatingWikidataClaims (to do). If that's the case, show a dedicated dialog to retry publishing the structured data and hide the draft itself (as the file is effectively uploaded and public now).