[Enhancement] CurseForge upload support "manual releases"

[UpcraftLP]

Curseforge added a new boolean to their release metadata to mark files for manual release. This means that the file will not be published immediately when approved, but has to be manually published later by the author (thus decoupling the approval process from when a file becomes available to the public).
See below screenshot for details and API documentation.

Click to expand screenshot of original announcement in the Curseforge discord

It would be nice to have some kind of curseforgeManualRelease property to file uploads that sets the relevant field in the upload form

[Kir-Antipov]

While I'm generally very skeptical about adding any more inputs to mc-publish, this is actually a very good opportunity to improve the existing ones. Currently, there's a GitHub-specific property named draft, which does exactly what's advertised - if it's set to true, mc-publish creates an unpublished draft of a release for you to publicize later.

With CurseForge enabling a similar scenario via their new isMarkedForManualRelease field (wow, they made 24 mistakes while spelling the word "draft"), I can finally create a standardized top-level draft property applicable to all currently supported platforms (I believe Modrinth also allows publishing drafts if one sets status to "draft" during version creation).

So, yeah, this is definitely going to be a part of the next release! :)