Path to deployment to staging

[bdach]

This is a list of things I see as required to be done before trying to put this thing on staging. Mostly adding for myself, but also for external accountability / tracking.

Tasks

Preview Give feedback

1. Add initial project contents #1
   size/XXL +1
   
2. Add tables for beatmap versioning support osu-web#11668
   area:beatmap-processing +1
   
3. Adjust versioning database code to schema changes #3
   size/M +1
   
4. Add various user- and beatmapset-related sanity checks to submission operations #4
   size/XL +1
   
5. Add various sanity checks concerning contents of beatmap package #5
   size/XL +1
   
6. Accept pending / WIP user choice on submission #6
   size/L +1
   
7. Automatically create beatmap set description topic on edit if missing osu-web#11706
   area:beatmap-info +1
   
8. Replace compound primary key on beatmapset_version_files with synthetic one osu-web#11709
   area:beatmap-processing +1
   
9. Issue required LIO calls to web #7
   size/L +1
   
10. Fix a few oversights #8
    size/M +1
    
11. Adjust guest difficulty submission logic to new beatmap owners structure #9
    size/M +1
    
12. Implement restoring beatmaps from graveyard #10
    size/L +1
    
13. Add submission-relevant events to database via LIO endpoints osu-web#11741
    area:beatmap-processing +1
    
14. Add submission-relevant events to database via LIO endpoints #11
    size/S +1
    
15. Optimise package-related operations #12
    size/L +1
    
16. Implement S3 beatmap storage #13
    size/L +1
    
17. Implement required interactions with beatmap mirrors #14
    size/L +1
    
18. Improve observability by integrating sentry, datadog, and adding extended logging #15
    size/XL +1
    
19. Investigate rate limiting possibilities (https://github.com/bdach/osu-server-beatmap-submission/commit/58a7211d32e8b159a670a1da76e59e0a4dbba8d6)