1. Proposed title of this feature request
Add annotation to ingress object for insecureEdgeTerminationPolicy configuration on the route.

2. What is the nature and description of the request?
At the moment we have two annotations to allow customers to configure the TLS termination and destination CA in the route from an ingress object. However looking at the code the 'spec.tls.insecureEdgeTerminationPolicy' is not configurable and it will always use Redirect policy.
Even though it is possible to configure the route afterwards customers would like to be able to have route TLSconfig automated as much as possible.
In that regard we could create an annotation like:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: frontend
annotations:
route.openshift.io/termination: "<value>"
route.openshift.io/destination-ca-certificate-secret: <secret-ca-cert>
route.openshift.io/insecure-edge-termination-policy: <Allow|Redirect|None>
spec:
[...]

3. Why does the customer need this? (List the business requirements here)
This affects customers' automation processes and they can't take advantage of this feature of converting ingress objects into OPenshift routers. Like now customers need two step and manual approach if they need different termination policies.

4. List any affected packages or components.
Openshift router-controller-manager