LittleBigRefresh/Refresh

This endpoint is intended to reset the user's progress on all pins. Unfortunately, unlike /reset_pin_progress, this endpoint is only called by debug builds when using a specific debug option to nuke all pin progress. The endpoint route doesn't even exist on retail builds. However, we should implement this endpoint anyway, especially since we already want to implement progress nuking itself (see #1109).

Currently finding cheated scores is almost a matter of getting lucky and finding an outlier by stumbling on a cheated level. Would be cool to have: -A display of all of a users uploaded scores in the moderation page (which might not always mean much unless obvious (IE 4,000,000 in every level), but could at least be used to track the levels a person has submitted scores in and then examine placement level by level) (might also be useful for comments tbh) --'Purge from x day to y day' feature (some instances of users going wild on score cheating early on after connecting then calming down, could also see potential for the case of someone playing with another person who was score cheating) -Ability to disable scoring for a user entirely. I know restricted mode is a thing but sometimes the issue isn't comments/levels of a user but the trust being broken that a person will play fair. If we could disable scores for a user that would prevent the need for monitoring past offenders while also

Occasionally, users (especially newer users) tend to forget their role or game preferences (whether their grief reports redirect, modded/reuploaded level filtering etc), and they also tend to not think of looking them up on the website. This has already left them confused a lot of times (like wondering why they can no longer see reuploads, or trying to actually grief report something and having their report be uploaded to public photos instead). One way to avoid this could be to show the user's account state (role, permissions, game preferences) on the announcements screen every time they log into the game. Additionally, we could also use LBP1's news feature (#851), or LBP2/3's recent activity news post feature (#1101). Besides reminding users, this would also be a quality-of-life feature where you wouldn't have to run chat commands to be extra sure of your preferences, and you wouldn't have to spend extra time looking your state up on the website. We could also make this be an opt-out

It'd be practical to, alongside keeping read-only as a master-switch to block any UGC, to also have several toggles to block uploads/edits of individual UGC types like levels, scores, comments etc. for certain role groups.