Move ingress-canary DaemonSet to Deployment and reduce the number to 2 or 4 replicas

1. Proposed title of this feature request
Move ingress-canary DaemonSet to Deployment and reduce the number to 2 or 4 replicas

2. What is the nature and description of the request?
The ingress-canary DaemonSet is currently expected to run on all OpenShift Container Platform 4 - Node(s) part of a OpenShift Container Platform 4 - Cluster. In large OpenShift Container Platform 4 - Clusters with many different shards this is adding unnecessary load/overhead to OpenShift Container Platform 4 - Node(s) as currently only the default IngressController is checked.

Hence it's requested to move the ingress-canary DaemonSet to a Deployment with about 2 to 4 replicas that allows configuration of NodeSelector and Toleration. That way, the footprint becomes smaller, the customer can run it where needed and desired and we can avoid running it on +300 OpenShift Container Platform 4 - Node(s) to just check the default IngressController

3. Why does the customer need this? (List the business requirements here)
Running +300 instances of the ingress-canary DaemonSet is not feasible to simply check availability and functionality of the default IngressController. Hence reducing the number of pods related to ingress-canary would be desired to minimize the overhead provided by the platform and instead use the resource for customer workload.

4. List any affected packages or components.
Ingress-Operator