Overview of the Feature Request

Four integration test classes pass against the CI stack but never run, because they aren't listed in tests/integration-tests.txt:

Adding them to the list gives 9 more tests in CI for about 10 seconds.

What kind of user is the feature intended for?

Developers.

What inspired the request?

While working on the CI pipeline in #12782 / #12783, we ran some experiments in our fork (uncch-rdmc/dataverse):

1. Run every *IT class without the list (uncch-rdmc/dataverse#104, run). Failsafe found the classes by name instead of reading tests/integration-tests.txt. 27 of the 80 *IT classes aren't in the list. Most were excluded for a reason: they need Testcontainers or outside services, they're @Disabled, or they fail against the CI stack. Five unlisted classes passed in all three jobs.
2. Add those five to the list (uncch-rdmc/dataverse#105, run). All five passed, but DataRetrieverApiIT then failed in every job. The cause is IpGroupsIT: it grants roles to an IP group covering 0.0.0.0–255.255.255.255, and its own source warns that it inflates the collection counts other tests assert. So it's correctly left out.
3. Add only the other four (same PR, run). Every job was green: 416 integration tests run, 0 failures, 15 skipped (was 407 / 0 / 15), and DataRetrieverApiIT passed.

What existing behavior do you want changed?

Add DataCiteIT, SignedUrlAuthMechanismIT, SiteMapIT and StorageSitesIT to tests/integration-tests.txt.

Any brand new behavior do you want to add to Dataverse?

No.

Any open or closed issues related to this feature request?

12782

Are you thinking about creating a pull request for this feature?

Yes, a pull request will follow.