adding cve finding and adding release-notes to PR template (#8916)

* adding cve finding and adding release-notes to PR template

Signed-off-by: James Strong <strong.james.e@gmail.com>

* update cve report with verbiage around open CVEs and not disclosures

Signed-off-by: James Strong <strong.james.e@gmail.com>

* fix then assignees

Signed-off-by: James Strong <strong.james.e@gmail.com>

Signed-off-by: James Strong <strong.james.e@gmail.com>

.github/ISSUE_TEMPLATE/cve_report.md

@@ -0,0 +1,20 @@
+---
+name: CVE Finding Report
+about: CVE reporting for ingress-nginx
+title: ''
+labels: kind/bug
+assignees:
+    - strongjz
+    - rikatz
+---
+
+<!-- if you found something that impacts directly ingress-nginx and 
+is not a public CVE yet, please reach out security@kubernetes.io" -->
+
+<!-- What scanner and version reported the CVE? -->
+
+<!-- What CVE was reported in the scanner findings? -->
+
+<!-- What versions of the controller did you test with?  -->
+
+<!-- Please provider other details that will help us determine the severity of the issue -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -15,8 +15,6 @@ The announcement in the dev mailing list is here https://groups.google.com/a/kub
 
 Thank you,
 Ingress-Nginx maintainer
-
-
 -->
 
 <!-- What do you want to happen? -->