IQSS/10793 Improve Handling of Parallel Edit/Publish errors

[qqmyers]

What this PR does / why we need it: This PR catches the OptimisticLockExceptions caused by an edit or publish attempt on a dataset that has been changed since the dataset page view was created and provides clearer error messages indicating what happened and how to recover. In addition to the error messages:

• for the Edit Metadata case, this PR causes the display to stay on the metadata edit/terms edit page to allow users to copy their text before it disappears.
• for the Publish case, the Publish lock is removed if an OptimisticLock occurs, so the user is able to refresh the page and try again.

Which issue(s) this PR closes:

Closes #10793

Special notes for your reviewer: I think the double refresh on the terms page was added when the check for file access requests allowed or terms of access required logic was added in #8308 where both the original commandButtons and the new remoteCommand for saving terms do update=":datasetForm,:messagePanel"

Suggestions on how to test this: Pretty easy to load two windows for the same dataset, make an edit in one and save and then make an edit to metadata/terms/etc. or try to publish in the other. Since this PR mostly updates the error messages, I hope that other changes on the page work ~as before/hopefully better with the new error messages, but I haven't tried all the buttons.

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?: added

Additional documentation: I only saw one line in the user guide that says you can edit metadata (at the end of the Add New Dataset section) and it seems like this is too much of a corner case to add to that. If there was a whole edit section telling you how to do that, adding a sentence to say you should avoid editing in two windows might make more sense. Or maybe we need a FAQ?

[coveralls]

coverage: 20.864% (-0.005%) from 20.869%
when pulling 8a3fe73 on GlobalDataverseCommunityConsortium:IQSS/10793-handle_optimisticlockexceptions
into a0cb73d on IQSS:develop.

[pdurbin]

I didn't run the code but it looks good to me. Catching more exceptions. New messaging about what's going on. Approved.

[ofahimIQSS]

Testing Completed - no issues were observed.
https://drive.google.com/file/d/1JzJu04qaSVtMMT7u7Xc3MW7qJWGhnCmz/view?usp=drive_link