Once we have the operator fork in https://github.com/openshift-service-mesh organization, we have to create versions.yaml and values.yaml files for product builds.

AC:

• it's possible to switch between upstream and downstream files when building manifests (e.g. using env variables VERSIONS_FILE, VALUES_FILE, or Makefile.overrides)
• new files must not break updates done by Automator
• we have up to date manifests for both upstream and downstream
• downstream versions.yaml should not contain 'latest' but only supported versions
• cpaas is configured to use generated downstream manifests from the fork repo