🐛 Address install plan upgrade with deprecated CRD flake

[perdasilva]

Description of the change:
The upgrade flow is tested by:

1. Creating a bundle which owns v1alpha1 of its CRD, which is the version served
2. Creating a subscription to the package and installing the first bundle
3. Updating the catalog by adding the next version: v1alpha2 (served), v1alpha1 (not served)
4. After the install plan installs the new CRD, the old CSV goes from Succeeded -> Failed -> Pending because v1alpha1 is no longer served
5. The new CSV expects the old CSV to be in a Replacing state, which it isn't

Trying to address this issue by adding a replacement check to the pending state on the CSV phase graph to kick it into Replacing.

Motivation for the change:

Architectural changes:

Testing remarks:

Reviewer Checklist

• Implementation matches the proposed design, or proposal is updated to match implementation
• Sufficient unit test coverage
• Sufficient end-to-end test coverage
• Bug fixes are accompanied by regression test(s)
• e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
• tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
• Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
• Docs updated or added to /doc
• Commit messages sensible and descriptive
• Tests marked as [FLAKE] are truly flaky and have an issue
• Code is properly formatted