What's the problem this feature will solve?

It would be nice to have integration tests focusing on the usage of setuptools "public API" by some popular packages in the community.

This way we can catch breaking changes in the API before publishing new releases

Describe the solution you'd like

According to the discussion in #2844, if adding a new "integration test suite", the following characteristics are desirable:

1. It should run separated from the main test suite (integration tests are resource intensive and time consuming, so the best is to avoid always running them and postponing until a new release is ready).
2. It should test how setuptools' API is being used by popular packages in the community to catch rare errors.

Alternative Solutions

No response

Additional context

No response

Code of Conduct

• I agree to follow the PSF Code of Conduct