`mindependency` should rationalize updated dependencies against `dev_requirements.txt`

[scbedd]

With the newest merge of azure-core==1.31.0, we have begun to see a new mindependency failure across our pipelines.

Failure

The failure occurs when:

• a given package has a dev_requirement on a local version of azure-identity...indicating a very NEW azure-identity
• The given package has a direct dependency against azure-core

The issue is that the local-relative-path version of azure-identity requires azure-core>=1.31.0. When we resolve mindependencies for azure-core, we'll resolve some version of azure-core PRIOR to azure-core==1.31.0. On installation, we will fail.

To resolve this we need to make the following adjustments:

• When grabbing the packages that will be the "minimum dependencies", we ALSO parse the requirements from these minimum dependencies
• If a given requirement conflicts with a dev_requirement, we should remove the line with that conflicting dependency from the dev_requirement file.

[scbedd]

This was fixed in #37669