to deploy opa using default values from helm chart

* comment out line 7-13 to not use default policy
   provided in the bundle

* enabled configmappolicies for namespace opa
  line 72-73

* defined variables for the opa and kube-mgmt image tags

To apply opa policies under resources/opa

This applies a ConfigMap that contains the
main OPA policy and default response.

This policy is used as an entry-point for policy evaluations and returns allowed:true
if policies are not matched to inbound data.

This policy prevents Ingress objects in different
namespaces from sharing the same hostname

ingress-conflicts policy necessary restrictions/permissions

* updated admissionControllerRules:
line 26-29 to restrict the kinds of operations
and resources that are subject to ingress-conflicts policy checks

* mgmt/replicate:
line 79-81 configured to pull resource
 metadata that needed for ingress-conflicts policy

*rbac:
line 113-139 ClusterRole permissions needed for ingress-conflicts policy

#242

Use := for assignment and == for equality. This makes the policy easier to read and is recommended practice. The
previous policy would fail to run properly in the opa repl.

Additionally, it removes the operation type check (redundant, we want to check both CREATE and UPDATE) which is set at
the ValidatingWebhookConfig level. Also removes the namespace check (which invalidates the check for ingresses within
the same namespace).

There is no need to override the values from terraform. Removing them makes maintainance easier since we don't need to
remember to update those values and can rely on defaults.