Dependencies filter available versions based on prerelease state of initial requirement

[scbedd]

During processing of latest/mindependency, we have the following flow:

• Walk requirements for the package under focus
  • azure-ai-evaluation triggered this investigation due to the weird behavior around httpx resolving > 1 and being incompatible with openai install - breaking latestdependency installation for azure-ai-evaluation.
• For each dependency package, grab the available versions from package manager
  • if there are any overrides in place for this package (eg overrrides on minimum version of msrest), apply those filters to the versions coming back from the package manager.
• Choose either the minimum or latest version from the list that make it through filtering, that is selected version for that dependency during the run.

This PR adds an additional step before processing the bounded versions -> filter out any packages that are prerelease if the specifier is not prerelease itself.

Frankly this has been like this a long time, I'm surprised it's taken this long to break.

As for origin, I have a suspicion that the behavior change is due to this PR: https://github.com/Azure/azure-sdk-for-python/pull/41973/changes#diff-3ea00033d292b993f07eec44e7472a93982f8275a6025c20df7423f067a1c1ca

[Copilot]

Pull request overview

This pull request adds prerelease filtering to the dependency resolution process used during latest/mindependency workflows. The changes address an issue where prerelease versions were being selected when they shouldn't be, which was causing installation failures (specifically with azure-ai-evaluation due to httpx/openai compatibility issues).

Changes:

• Added logic to filter out prerelease package versions unless the dependency specifier explicitly allows them
• Minor code formatting improvements (compressing multi-line list comprehensions to single lines)
• Added trailing comma to dictionary definition for consistency

[scbedd]

Nightly core tests checking out. Merged.