10112-ProvIT-enable-fix

[jp-tosca]

What this PR does / why we need it:
The ProvIT test is not working correctly due to the feature not being enabled.

Which issue(s) this PR closes:

Closes #10112

Special notes for your reviewer:
This change will enable the feature and delete the setting at the end of the test.

Suggestions on how to test this:

1. Check out the repo
2. Start docker, mvn -Pct clean package docker:run
3. Run the test, mvn test -Dtest=ProvIT

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

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

Additional documentation:
N/A

[jp-tosca]

I made an additional change to this PR; Initially, I expressed concerns by messing with permanent settings during the test.

The first change enables and then disables the provenance collection setting, this prevents the test from failing but then I realized by doing this, that if the setting was initially on, running this test would leave it off.

I decided to check the status of the setting and only enable it if it wasn't initially, and then disable it only if it was modified during the test.

This may not affect this test but probably if someone else is using this setting is better just to leave it on the status that it was found before the test.

[pdurbin]

In 3407fb9 I enabled the test to run automatically in our CI. For more on the file I edited: https://guides.dataverse.org/en/6.0/developers/testing.html#writing-api-tests-with-rest-assured

Update: it passed. See https://jenkins.dataverse.org/job/IQSS-Dataverse-Develop-PR/job/PR-10113/3/testReport/edu.harvard.iq.dataverse.api/ProvIT/

[pdurbin]

https://jenkins.dataverse.org/job/IQSS-Dataverse-Develop-PR/job/PR-10113/4/ failed but I made a couple formatting commits and will re-check after the API tests run.

[pdurbin]

Tests are passing at https://jenkins.dataverse.org/job/IQSS-Dataverse-Develop-PR/job/PR-10113/5/testReport/edu.harvard.iq.dataverse.api/ProvIT/

I'm merging this.