Update the release issue template (#2218)

Author: Amulyam24

.github/ISSUE_TEMPLATE/release.md

@@ -15,5 +15,13 @@ After every CAPIBM major version release:
 - [ ] [Update release support data in docs](https://github.com/kubernetes-sigs/cluster-api-provider-ibmcloud/blob/main/docs/book/src/developer/release-support-guidelines.md)
 - [ ] [Update docs with reference to latest release](https://github.com/kubernetes-sigs/cluster-api-provider-ibmcloud/blob/main/README.md#compatibility-with-cluster-api-and-kubernetes-versions)
 - [ ] Update and add documentation link for new release branch in Netlify
-- [ ] Add new presubmit job for latest release kubernetes/test-infra for CAPIBM jobs
-- [ ] Bump machine images in CI to use relevent Kubernetes version
+- [ ] Add new presubmit job for latest release branch in [kubernetes/test-infra](https://github.com/kubernetes/test-infra/tree/master/config/jobs/kubernetes-sigs/cluster-api-provider-ibmcloud)
+    - [ ] Update kubekins-e2e image to relevent Kubernetes version
+- [ ] Add E2E CI jobs for latest release branch in [ppc64le-cloud/test-infra](https://github.com/ppc64le-cloud/test-infra/blob/master/config/jobs/periodic/cluster-api-provider-ibmcloud/test-e2e-capi-ibmcloud-periodics.yaml)
+    - [ ] Bump machine images in CI to relevent Kubernetes version
+    - [ ] Update kubekins-e2e image to relevent Kubernetes version
+
+> Note:
+> 1. An example for infrastructure provider version upgrade, if we cut a release for version
+> 0.9.0, update the infratructure provider version to 0.10.0 on the main branch.
+> 2. Keep the version upgrades in check for the main branch and the two latest releases.