Remove check for package-level incompatible override when running pac…

[chayac]

…kage upgrade

Description

Please describe the changes made and why they were made. Link to any relevant issues or tickets.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist

• Ran uvx ruff@0.14.14 check . --config pyproject.toml
• Ran uvx ruff@0.14.14 format --config pyproject.toml
• If this is a bug fix:
  • Updated integration tests with bug repro
  • Linked to bug report ticket
• Added unit tests if needed
• Updated unit tests if needed
• Tests passed when run locally

[davidharting]

In this state, does this mean we would no longer consider the explicit disallow list when upgrading packages, but we still would use it when:

• Determining manually_verified_incompatible during parse conformance
• Determining if a package needs to be upgraded during the packages subcommand

edit - asking bc I'm trying to get my head around what removing EXPLICIT_DISALLOW_LIST entirely would look like when the time comes!

[davidharting]

I think should close #343