This will allow for a standardized collection of Strings
thus avoid typos

This extension allows to set and reset database settings within
a target Dataverse instance. It will make sure to reset to
old setting or remove the setting if not set before the test.

This was introduced for three reasons:
1. Don't execute a test if the setting did not go through
2. Don't forget to reset or remove to keep a consistent state after a
   test execution
3. Make the code more readable, as setting the setting has been part of
   the test before (which is bad design and might go booboo, see 2)

…IQSS#8251

When no stored procedure has been set up in the instance under test,
test running after
DatasetsIT.testStoredProcGeneratedAsIdentifierGenerationStyle() failed,
as the database setting was never reverted.

Making use of the new @DBSetting extension helps with that.

Many API tests require the use of a random user, which is no SuT
(subject under test). To gather such a user and ensure its deletion
from a target Dataverse instance after a test, this extension
provides a convenient way. Simple use ExtendWith and provide a
RandomUser parameter, you're done.

This helper class tries to abstract the store retrieval and handles all
the tiny details on retrieving in-depth context for a store.

With this commit, the RandomUserExtension may be used on
a test class, @BeforeEach/All, @AfterEach/All methods and
test methods.

It will take care of deletion in the appropriate ways to ensure a
healthy target environment.

Using it on @AfterEach/All will return the formerly created user via
@BeforeEach/All and enabled aftermath reuse of the user.

…o that only the terms of use and access are considered (and not the guestbook which should only be considered at file download in isDownloadPopupRequired).

…QSS#6725]"

This reverts commit 1e5951f.

"application/octet-stream" is the default when the user doesn't supply a
content type. So if it's this, send it through Tika. Yes, a user
can supply "application/octet-stream" and this will also be sent through
Tika.

This avoids an NPE when the empty embargo (from the dialog that isn't
shown) is found to be invalid and then getMaxDate() returns null and the
code tries to format it for display in the error message (which also
wouldn't show).

… to 3.8.4

verified that the names withheld bundle entry already exists.

Update to v5.9

Update to v5.9

Update to v5.9