Add flags to configure controller parameters

[sushrk]

Issue #, if available:
#451 partly

Description of changes:

1. Add support to configure controller parameters via flags, flags added

nodeWorkerCount: The number of node workers, default 10
userClientQPS: The EC2 user client QPS rate, default 12
userClientBurst: The EC2 user client burst limit, default 18
instanceClientQPS: The EC2 instance client QPS rate, default 12
instanceClientBurst: The instance client burst limit, default 18
apiServerQPS: The API server client QPS rate, default 20
apiServerBurst: The API server client burst limit, default 30
maxPodConcurrentReconciles: The maximum number of concurrent reconciles for pod controller, default 20
maxNodeConcurrentReconciles: The maximum number of concurrent reconciles for node controller, default 10

Customers can configure these values via controller flags eg here when running the controller on dataplane or non-EKS CP. Controller on EKS will use the defaults defined above.

- --node-mgr-workers=xx
- --user-client-qps=xx
- --user-client-burst=xx
- --instance-client-qps=xx
- --instance-client-burst=xx
- --apiserver-qps=xx
- --apiserver-burst=xx
- --max-pod-reconcile=xx
- --max-node-reconcile=xx

Verified controller is able to run, SGPP tests passed:

Ran 18 of 22 Specs in 1190.175 seconds
SUCCESS! -- 18 Passed | 0 Failed | 0 Pending | 4 Skipped
PASS

2. Changed to r.Log.Info("branch ENI cool down period not configured in amazon-vpc-cni configmap, will retain the current cooldown period", "cool down period", curCoolDownPeriod) to avoid logging benign errors in the controller and make it easier to parse error logs.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[yash97]

lgtm 🚀