Pip doesn't raise on package conflict in extras_require

[slanton-a]

Description

I have a service that is installing some internal and external packages. In the internal package I have a few extras_require and in the service I have a package that is in conflict with extras_require.
I expect to see this conflict when running pip check

Expected behavior

pip check will display a conflict on the package tenacity. It does show it as conflict if I move it from extras_require to install_requires

pip version

24.0

Python version

3.10

OS

Ubuntu 20.04.6 LTS

How to Reproduce

1. Have an internal package, called: pack_a with the following info in setup.py

b_dependencies = [
    'pyarrow>=6.0.0, <=12'
]

c_dependencies = [
    'tenacity>=8.2.3'
]

setup_config = {
    "name": 'pack_a',
    "version": '0.0.1',
    "python_requires": '>=3.7',
    "packages": setuptools.find_packages(),
    "include_package_data": True,
    "extras_require": {
        "b": b_dependencies,
        "c": c_dependencies
    },
}

2. Have a service requirements (tenacity==8.0.1) in requirements.txt file
3. In the same service, list Internal packages in requirements-internal.txt as install from git with pack_a[b,c] @ git+https://github.com/*****/pack_a.git@0.0.1
4. Install all packages with pip install -r requirements.txt -r requirements-internal.txt --no-deps
5. run pip check
6. See no conflicts on tenacity package

Output

No broken requirements found.

Code of Conduct

• I agree to follow the PSF Code of Conduct.

[ichard26]

See also #4086.