A workaround for the annoying "draft not found" after a successful completion of async. publishing

[landreev]

What this PR does / why we need it:

This has been annoying users for years now (#8136 #7653 #8548... there are possibly more that I couldn't find right away). This 3-line workaround makes it less annoying.

Which issue(s) this PR closes:

It may be debatable whether it actually "closes" the issue below. I am selling it as a "workaround" only. But it definitely improves the user experience; and we likely don't want to invest any more effort than this into a jsf page at this point. So may as well close it.

• Closes When publishing a version, there is a confusing message on page reload #8136
• Closes Dataset Publish - Missing success msg + broken tooltips and other js rebind functions + unfortunate "DRAFT was not found" on page reload #7653
• Closes Dataset page stays on the url with "version=DRAFT" after the dataset is published #8548
• Closes Publishing and dataset landing page: Once a dataset is published, the draft URL and draft message should disappear #11866

Special notes for your reviewer:

Suggestions on how to test this:

Prior to this build: publish a dataset; when the async. publishing process completes in the background and the lock disappears, the url in the browser location bar will still have "version=DRAFT" in it. You may or may not see the yellow "draft not found, verison such and such shown instead" warning at this point. Try to reload the page - now you will be presented with the annoying yellow message. (Apparently that's what real life users keep doing: instead of manually removing the "version=" parameter from the url, they keep reloading the page, hoping that it will go away - and keep seeing the warning message again...)

With this build deployed: you should not be seeing the yellow warning message at any point during the publishing process. Reloading the page will quietly send you to the now published version. (Assuming publishing has actually worked; if it has failed for whatever reason, you will stay on your draft version, which is what we want)

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?:

Additional documentation:

[landreev]

(this is already in the HDV 6.8 prod. patch deployed)

[coveralls]

coverage: 23.798% (-0.001%) from 23.799%
when pulling eed5e67 on 8136-annoying-draft-message-after-publishing
into c6ccf87 on develop.

[stevenwinship]

Tested:
Original code did show DRAFT in url and yellow Draft not found message when reloading
New code brought up published version when reloading the url with version=DRAFT

[stevenwinship]

Tested reloading while the publish was taking place. Draft shows until publish finishes. Then published version shows. Nice!

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:8136-annoying-draft-message-after-publishing

ghcr.io/gdcc/configbaker:8136-annoying-draft-message-after-publishing

🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name.