examples: Update AWS ELB config

- Remove incorrect `aws-load-balancer-internal`.
- Sets `aws-load-balancer-scheme: internet-facing`.
  This is match what our examples expect.
- Change the loadbalancer for Grafana from "CLB" (Classic) to "NLB"
  (Network)

Related:
- pingcap#3941

examples/aws/tidb-cluster.yaml

@@ -47,8 +47,8 @@ spec:
     service:
       annotations:
         service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: 'true'
-        service.beta.kubernetes.io/aws-load-balancer-internal: '0.0.0.0/0'
-        service.beta.kubernetes.io/aws-load-balancer-type: nlb 
+        service.beta.kubernetes.io/aws-load-balancer-type: nlb
+        service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing
       exposeStatus: true
       externalTrafficPolicy: Local
       type: LoadBalancer

examples/aws/tidb-monitor.yaml

@@ -22,7 +22,12 @@ spec:
     logLevel: info
     password: admin
     service:
-      portName: http-grafana
+      annotations:
+        service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: 'true'
+        service.beta.kubernetes.io/aws-load-balancer-type: nlb
+        service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing
+      exposeStatus: true
+      externalTrafficPolicy: Local
       type: LoadBalancer
     username: admin
     version: 6.1.6