Add recovery mechanism for submission of beatmaps with deleted IDs

[bdach]

There have been some reports of cases where a beatmap submission can't go through because of the .osu files containing bogus (read: deleted) IDs.

Off the top of my head, I don't see any reason not to offer a facility to reset the IDs and try with a new one in such a case.

The handling of this should be based around detecting this condition:

https://github.com/ppy/osu-server-beatmap-submission/blob/fd759f7df35e4e5b61faacbd39489572cbe10003/osu.Server.BeatmapSubmission/BeatmapSubmissionController.cs#L102-L103

e.g. if this 404s, the user should be told about the bad IDs and asked if they want to reset the IDs and try with a new set. (This is why I'm opening this client-side rather than just handle server-side, I think this should be an interactive decision of the user.)

Not planning to act on this imminently, therefore logging as issue.

[bdach]

Similarly to this, there are cases where because of the use of external tools, a local difficulty is dissociated from its online counterpart because the game can no longer identify it as being the same thing. A case of this is here, where a user exported a beatmap, edited it externally to the game in another tool, re-imported it and attempted to update it. This failed spectacularly because the game could not match any of the difficulties against online sources:

2025-08-16 12:43:36 [verbose]: [82c9e] Found existing beatmap set with same OnlineID (1874228). It will be disassociated and marked for deletion.
2025-08-16 12:43:36 [verbose]: [82c9e] [APIBeatmapMetadataSource] Online retrieval failed for -45 - Reikou Hatsuden (Florescence) [Industria]
2025-08-16 12:43:37 [verbose]: [82c9e] [APIBeatmapMetadataSource] Online retrieval failed for -45 - Reikou Hatsuden (Florescence) [Insane]
2025-08-16 12:43:37 [verbose]: [82c9e] [APIBeatmapMetadataSource] Online retrieval failed for -45 - Reikou Hatsuden (Florescence) [Advanced]
2025-08-16 12:43:37 [verbose]: [82c9e] [APIBeatmapMetadataSource] Online retrieval failed for -45 - Reikou Hatsuden (Florescence) [Hard]
2025-08-16 12:43:37 [verbose]: [82c9e] [APIBeatmapMetadataSource] Online retrieval failed for -45 - Reikou Hatsuden (Florescence) [Easy]
2025-08-16 12:43:38 [verbose]: [82c9e] [APIBeatmapMetadataSource] Online retrieval failed for -45 - Reikou Hatsuden (Florescence) [Impetus]
2025-08-16 12:43:38 [verbose]: [82c9e] [APIBeatmapMetadataSource] Online retrieval failed for -45 - Reikou Hatsuden (Florescence) [nine's Light Insane]
2025-08-16 12:43:38 [verbose]: [82c9e] [APIBeatmapMetadataSource] Online retrieval failed for -45 - Reikou Hatsuden (Florescence) [magn3ta's abnormal]
2025-08-16 12:43:38 [verbose]: [82c9e] [APIBeatmapMetadataSource] Online retrieval failed for -45 - Reikou Hatsuden (Florescence) [Extra]
2025-08-16 12:43:39 [verbose]: [82c9e] [APIBeatmapMetadataSource] Online retrieval failed for -45 - Reikou Hatsuden (Florescence) [Extreme]
2025-08-16 12:43:39 [verbose]: [82c9e] [APIBeatmapMetadataSource] Online retrieval failed for -45 - Reikou Hatsuden (Florescence) [Normal]
2025-08-16 12:43:39 [verbose]: [82c9e] Import successfully completed!
2025-08-16 12:43:39 [verbose]: Beatmap "-45 - Reikou Hatsuden (Florescence)" update completed successfully
2025-08-16 12:44:27 [verbose]: [BeatmapSubmissionScreen] Updating existing beatmap set (id:1874228 beatmapsToKeep:[] beatmapsToCreate:11)
2025-08-16 12:44:28 [verbose]: [BeatmapSubmissionScreen] Export failed: System.InvalidOperationException: Difficulty "Insane" has BeatmapID 4910475 that has not been assigned to it by the server!

Partially this is made worse by the fact that we cannot use online IDs for any of this logic because mappers were so "kind" as to abusively reuse online IDs in bogus ways to bypass submission failures in stable BSS.

In those cases the difference between the state of the online beatmap and the local beatmap should be communicated to the user and the user should be permitted to re-associate the beatmaps with their online counterparts again.

[peppy]

One thing to be wary of here is that we do want to attempt to keep relationships where we can. Resetting to new autoincrements will mean losing favourites, mod discussion history etc.

I think a recovery process where beatmaps are re-matched using best-effort metadata matching would work fine though. Handling cases where difficulty names change is the hardest part.