`upgrade-test --conflict-test` does not work with Astro Runtime 8.8.0

[manmeetkaur]

Describe the bug

When we run the Conflict test without passing any Runtime version, the most recent version is picked up. Then the conflict-test fails.

#15 288.4   The conflict is caused by:
#15 288.4       The user requested proto-plus==1.19.6
#15 288.4       apache-airflow-providers-google 10.0.0 depends on proto-plus==1.19.6
#15 288.4       google-ads 21.2.0 depends on proto-plus<1.23 and >=1.19.6
#15 288.4       google-cloud-aiplatform 1.16.1 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-appengine-logging 1.1.3 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-automl 2.8.0 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-bigquery 2.34.4 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-bigquery-datatransfer 3.7.0 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-bigquery-storage 2.14.1 depends on proto-plus<2.0.0dev and >=1.18.0
#15 288.4       google-cloud-bigtable 2.11.1 depends on proto-plus<2.0.0dev and >=1.18.0
#15 288.4       google-cloud-build 3.9.0 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-compute 0.7.0 depends on proto-plus>=1.13.0
#15 288.4       google-cloud-container 2.11.1 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-datacatalog 3.9.0 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-dataflow-client 0.5.4 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-dataform 0.2.0 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-dataplex 1.1.0 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-dataproc 5.0.0 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-dataproc-metastore 1.6.0 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-dlp 3.8.0 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-kms 2.12.0 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-logging 3.2.1 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-memcache 1.4.1 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-monitoring 2.11.0 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-orchestration-airflow 1.4.1 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-os-login 2.7.1 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-pubsub 2.13.5 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-redis 2.9.0 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-resource-manager 1.6.0 depends on proto-plus<2.0.0dev and >=1.15.0
#15 288.4       google-cloud-storage-transfer 1.9.1 depends on proto-plus<2.0.0dev and >=1.22.0
#15 288.4
#15 288.4   To fix this you could try to:
#15 288.4   1. loosen the range of package versions you've specified
#15 288.4   2. remove package versions to allow pip attempt to solve the dependency conflict
#15 288.4
#15 290.5 Traceback (most recent call last):
#15 290.5   File "/usr/local/lib/python3.10/site-packages/pip/_vendor/resolvelib/resolvers.py", line 316, in _backjump
#15 290.5     name, candidate = broken_state.mapping.popitem()
#15 290.5 KeyError: 'dictionary is empty'

What CLI Version did you experience this bug? The new Astro binary for 1.18.0

This CLI bug is related to which Astronomer Platform?

• [X] Astro
• [ ] Software
• [ ] None/Unknown

What Operating System is the above CLI installed on? M1 Mac

🪜 Steps To Reproduce

1. Go to your Astro project
2. Run astro dev upgrade-test --conflict-test

📸 Screenshots