doc: Amend release.md to note that the OLM manifests must also be cha…

…nged

The OLM manifests at examples/olm/install-resources.yaml contain
unversioned image tags, but at the release time they should contain the
release tag.

release.md

@@ -18,6 +18,8 @@ The first PR targets this repository and:
   `k8s.gcr.io/security-profiles-operator/security-profiles-operator` (`newName`) and the
   corresponding tag (`newTag`). After that the make target `make bundle`
   has to be run and the changes have to be committed.
+- changes the tag in the same way in the OLM example manifest at
+  [./examples/olm/install-resources.yaml](/examples/olm/install-resources.yaml)
 
 After this PR has been merged, we have to watch out the successful build of the
 container image via the automatically triggered
@@ -61,6 +63,8 @@ After that, another PR against this repository has to be created, which:
   [./deploy/base/kustomization.yaml](deploy/base/kustomization.yaml) back to
   `gcr.io/k8s-staging-sp-operator/security-profiles-operator` (`newName`) and `latest`
   (`newTag`).
+- changes the tag in the same way in the OLM example manifest at
+  [./examples/olm/install-resources.yaml](/examples/olm/install-resources.yaml)
 - runs `make bundle`
 
 The last step about the release creation is to send a release announcement to