Description of problem:

Users can configure custom catalog source in submarinerconfig when installing submariner addon instead of using the default one. In such scenarios Submariner will not upgrade when upgrading ACM to newer versions. This is because submarinerconfig is still configured to use older version of submariner.

Version-Release number of selected component (if applicable):

ACM 2.6 2.7 2.8

How reproducible:

Steps to Reproduce:

1. Create a custom CatalogSource for submariner during installation.
2. Upgrade ACM to newer version

Actual results:

Submariner components are still using older version from before upgrade.

Expected results:

Submariner components should use newer version after upgrade.

Additional info:

ACM 2.8 added UI support to configure custom CatalogSource. It should also validate that user is using the correct version for a given release.