API: deprecate toggle of superuser status in favor of new idempotent endpoint, update setup-all.sh

[zearaujo25]

What this PR does / why we need it:
Adds a new endpoint to make the superuser status change idempotent.
Which issue(s) this PR closes:

• Closes idempotent API call for making a user a superuser #9887

Special notes for your reviewer:
none

Suggestions on how to test this:
Integration test

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?:
New endpoint addition
Additional documentation:

Preview at https://dataverse-guide--10440.org.readthedocs.build/en/10440/api/native-api.html#set-superuser-status

[pdurbin]

Looks good! Thanks! Please see my comments.

[pdurbin]

I wasn't able to run the integrations tests locally as i keep receiving the java connection refused error

Huh. Please hit me up in https://chat.dataverse.org and I can try to help. I'll point you toward running Dataverse in Docker: https://preview.guides.gdcc.io/en/develop/developers/dev-environment.html#quickstart

Anyway, I know you can't see the results of Jenkins testing this pull request...

• Let contributors know why tests are failing #9916

... but here's a screenshot from https://jenkins.dataverse.org/job/IQSS-Dataverse-Develop-PR/job/PR-10440/1/testReport/edu.harvard.iq.dataverse.api/AdminIT/ that shows your tests (all tests, really) are passing:

[pdurbin]

A comment on deprecation.

[pdurbin]

This pull request is really coming together! Thanks, @zearaujo25 !

I left some more feedback for you.

[pdurbin]

A little more feedback.

[coveralls]

coverage: 20.705% (-0.002%) from 20.707%
when pulling 80ae69b on zearaujo25:feat/9887
into a0d7cd2 on IQSS:develop.

[pdurbin]

Quick question about curl.

Also, I merged develop into this branch.

[pdurbin]

@zearaujo25 and I chatted and we decided on the following:

• For consistency with the settings API, we'll switch to -X PUT -d true.
• We know the SPA will someday need the ability to promote and demote superusers (probably under /api/users) but we'll defer this for now.
• Since the toggle API is deprecated as of this PR, we will switch scripts/api/setup-all.sh to use it.
• Phil might switch an API test or two to the new PUT version.
• At some point, we should open an issue to migrate away from the POST version (tech debt).

[zearaujo25]

We know the SPA will someday need the ability to promote and demote superusers (probably under /api/users) but we'll defer this for now.

I also would like to add the supersuer feature for the SPA probably will need a restructure of endpoints logic. Since its too early to predict such changes, we opt to defer this feature when its clearer the needs the front end team will need

[pdurbin]

defer this feature when its clearer the needs the front end team will need

Yes, exactly. I did ping @ekraffmiller @GPortas @MellyGray and @GermanSaracca about this in Slack: https://iqss.slack.com/archives/C04MJ76A34Z/p1712942297281699

[pdurbin]

@zearaujo25 this is looking really good. Approved! Thank you!

To whoever does QA, I did a fair amount of testing and poking around. Please at least check that tests are passing and that the docs look ok.