Konflux fill in productized images to the CSV according to ENVs so CSV must have desired ENVs.

E.g. ENVs for 

1. 3.0 CSV https://gitlab.cee.redhat.com/istio/konflux/ossm/-/blob/ossm-3.0/bundle-patch/export-images-v3-0.sh 
2. 3.1 CSV https://gitlab.cee.redhat.com/istio/konflux/ossm/-/blob/ossm-3.1/bundle-patch/export-images-v3-0.sh?ref_type=heads and https://gitlab.cee.redhat.com/istio/konflux/ossm/-/blob/ossm-3.1/bundle-patch/export-images-v3-1.sh?ref_type=heads 

Update sail operator midstream CSV according to the release.
Every time when you are releasing older minor version (e.g. 3.0.z with istio 1.24.6 when we already have 3.1.z, 3.2.z, 3.3.z), you must update placeholders for that 1.24.6 images in the all newer CSV as well!

Different situations can happen according to the release:

1. One version release which contains a newer istio version
   1. The ENV should already be prepared in the CSV, since during istio version bumping, there were no productized images. ( otherwise, something is wrong ) 
2. One version release which contains the same istio version
   1. In this situation, the latest istio version images will be replaced by new one. So starting the release, change already released images back to ENV placeholders in `ossm/values.yaml` (and run `make gen`*) so konflux can update it
      1. e.g.: 3.0.4 release which had the same istio version, so only images must be refreshed: https://github.com/openshift-service-mesh/sail-operator/pull/450  
3. Multiple versions release at the same time (e.g. 3.0.4 & 3.1.1 ) 
   1. In this situation, multiple CSV files will be changed. For each newer version of CSV, there is change in both, actual and previous images. So this situation is combination of previous ones. 
   2. Examples when: 
      1. Some istio versions are same, some are not.
         1. Let's say we want to release 3.0.4 (istio 1.24.6) and 3.1.1 (istio 1.26.2), where 3.0.4 doesn't have istio version change but 3.1.1 has istio version change to 1.26.3
         2. change istio 1.24.6 images to back to ENV placeholders in `ossm/values.yaml` (and run `make gen`*) for the 3.0 CSV ( https://github.com/openshift-service-mesh/sail-operator/pull/450 )
         3. change istio 1.24.6 images to back to ENV placeholders in `ossm/values.yaml` (and run `make gen`*) for the 3.1CSV, for new istio version, the placeholders will be already prepared during upgrade istio version process ( TBD )
      2. All istio versions are same
         1. Let's say we want to release 3.0.4 (istio 1.24.6) and 3.1.1 (istio 1.26.2), where any 3.0.4 or 3.1.1 has newer istio version
         2. change istio 1.24.6 images to back to ENV placeholders in `ossm/values.yaml` (and run `make gen`*) for the 3.0 CSV
         3. change istio 1.24.6 and 1.26.2 images to back to ENV placeholders in `ossm/values.yaml` (and run `make gen`*) for the 3.1CSV

if you don't have docker cli, use `export BUILD_WITH_CONTAINER=0; make gen`, and if you see error like `license-lint: No such file or directory`, do not forget to install license-lint via `go install istio.io/tools/cmd/license-lint@v0.0.0-20250818115453-9718d40e2740` and make sure you have go bins on path `export PATH=${PATH}:`go env GOPATH`/bin`