Fix for #8053 - avoid setting lock on as-yet-uncomitted dataset

[qqmyers]

What this PR does / why we need it: Fixes the Dataverses datasets/:import and :importddi API calls when release=yes

Which issue(s) this PR closes:

Closes #8053

Special notes for your reviewer: These two API calls, with release=yes appear to be the only two cases where a dataset is being created and published within the same transaction. Unfortunately, updates to the Publish command to create a DatasetLock in a separate transaction (which allow setting the lock earlier than waiting for the Publish (and potential workflow starting) to complete) fail as shown in the issue in this case - as the dataset has not yet been committed. The solution here just avoids trying to set a lock in this case (as no one can be editing the Dataset yet anyway). Alternately, I did verify that running the initial Import/CreateDataset command in a separate transaction, so that it completes before Publish is called, would also work. This would mean that any real problem in the Publish command would result in the dataset being imported but not released/published - that might be useful, but it's a change in functionality, whereas avoiding the lock appears to not affect anything aside from fixing the bug.

Suggestions on how to test this: Use release=true in the :import and :importddi API calls

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

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

Additional documentation: I added notes in the code

[coveralls]

Coverage decreased (-0.0003%) to 19.144% when pulling 99a761e on GlobalDataverseCommunityConsortium:IQSS/8053-fix_import into 72c26e3 on IQSS:develop.