Explore clarified stage workflow for preprints in OJS

[asmecher]

Now that the basic JAV vocabulary has been added to OJS, and continuous publication / issueless publication is nearly there, we need to simplify/clarify some aspects of preprint workflows in OJS.

In particular...

• Posting a preprint requires a lot of unnecessary clicks, and
• Once a preprint is submitted, we need to ensure that the subsequent workflows on publishing a peer reviewed article make sense in the publishing queues.
• We need to make sure that file management doesn't get confusing. For example, if an author uploads a revision of a submission file two years after it first became a preprint, it should be easy to parse through the file list to see what's new.

[asmecher]

A hack-and-slash start at reducing clicks when posting a preprint...

• pkp/pkp-lib/discussions/11762 Allow posting right from submission (for preprints) ui-library#695
• pkp/pkp-lib/discussions/11762 Allow posting right from submission (for preprints) #11763

Results:
https://github.com/user-attachments/assets/15a1904b-6675-4a0c-b797-8931ebe8f212

[asmecher]

I went ahead with these 2 interventions in main -- they're minimal and really clean up the preprint publishing process.

[asmecher]

On potentially working versioning into the workflow: @Devika008, @jardakotesovec and I have been talking about possibly introducing some form of versioning into the file lists. The idea is that the files relevant to a particular version are grouped together, a bit like we group public comments by version. This needs some experimentation and design work.

[asmecher]

Editorial decisions: I pushed another change straight to main as it was trivial and solved a problem tidily.

094ccd7

Previously, editorial decisions could not be made to submissions that had a Submission::STATUS_PUBLISHED status. This was the main mechanism preventing workflow from continuing on posted preprints.