Allow crate version deletion in the first 24 hours from creation

[nappa85]

Adds route DELETE /api/v1/crates/:crate_id

Resolves #5293

[Turbo87]

@nappa85 just for awareness: #5293 (comment)

tl;dr I'm not sure whether we should allow crate deletion, or if it makes more sense for us to allow version deletion, and then if there is no version left the crate automatically gets deleted too.

[nappa85]

@nappa85 just for awareness: #5293 (comment)

tl;dr I'm not sure whether we should allow crate deletion, or if it makes more sense for us to allow version deletion, and then if there is no version left the crate automatically gets deleted too.

Updated, let me know if there is anything else

[Turbo87]

I think there is some work left on correctly syncing both the git and the http index after the deletion. But before we continue, I talked to a few people about this and since it is a quite significant change we might actually require to go through the RFC process for it since other people are currently relying on the fact that crates don't just disappear like that again.

[Turbo87]

and just to be clear, I'm very thankful for the quick implementation! I just want to make sure we're not we're not surprising too many people with this change :)

[nappa85]

and just to be clear, I'm very thankful for the quick implementation! I just want to make sure we're not we're not surprising too many people with this change :)

Understandable, don't worry

[bors]

☔ The latest upstream changes (presumably 802f7ec) made this pull request unmergeable. Please resolve the merge conflicts.

[nappa85]

Something nasty happened during the rebase, probably better restart from scratch...