Add four passing integration test classes to tests/integration-tests.txt

[ashmanda-cs]

What this PR does / why we need it:

Adds four integration test classes to tests/integration-tests.txt: DataCiteIT, SignedUrlAuthMechanismIT, SiteMapIT and StorageSitesIT. They pass against the CI stack but were never listed, so they never ran. That's 9 more tests in CI for about 10 seconds.

See #12815 for how they were found, and for why IpGroupsIT stays out of the list even though it passes on its own.

Which issue(s) this PR closes:

• Closes Add four passing integration test classes to tests/integration-tests.txt #12815

Special notes for your reviewer:

The only change is one line in tests/integration-tests.txt. The same change was verified in our fork, on top of #12783: run 38064623496 gave 416 integration tests run, 0 failures and 15 skipped in all three jobs (was 407 / 0 / 15).

Suggestions on how to test this:

In the integration test results of this PR's checks, confirm that the four classes ran and passed, and that the totals went from 407 to 416 with 0 failures.

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. It only changes which existing tests run in CI.

Additional documentation:

None.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[pdurbin]

Ideas:

• Use tags instead
• Exclusions list instead

[poikilotherm]

What if we finally replace the ever growing list with a proper Tag "api", enabling using them with a simple mvn verify -Dit.groups=api as we use for integration and performance tests?

Any test not working should be @Disabled or activated by adding another group to the list.

Would require documentation updates as well.

[ashmanda-cs]

What if we finally replace the ever growing list with a proper Tag "api", enabling using them with a simple mvn verify -Dit.groups=api as we use for integration and performance tests?

Any test not working should be @Disabled or activated by adding another group to the list.

Would require documentation updates as well.

I always loved this idea. Can we open a separate issue to track this?

[pdurbin]

Sure, here's a new, separate issue:

• Move away from manually updating tests/integration-tests.txt #12822