Update compute_security_policy docs to match src_ip_ranges constraints (#3808) (#2326)

The limit of 5 IP ranges per rule was increased to 10 in #3516. This commit updates the
related documentation.

Signed-off-by: Modular Magician <[email protected]>

Author: modular-magician

.changelog/3808.txt

@@ -0,0 +1,3 @@
+```release-note:none
+This only updates the description and website documentation. The functionality was already implemented and added to the release notes. No further mention in the release notes is necessary.
+```

google-beta/resource_compute_security_policy.go

@@ -89,7 +89,7 @@ func resourceComputeSecurityPolicy() *schema.Resource {
 													MinItems:    1,
 													MaxItems:    10,
 													Elem:        &schema.Schema{Type: schema.TypeString},
-													Description: `Set of IP addresses or ranges (IPV4 or IPV6) in CIDR notation to match against inbound traffic. There is a limit of 5 IP ranges per rule. A value of '*' matches all IPs (can be used to override the default behavior).`,
+													Description: `Set of IP addresses or ranges (IPV4 or IPV6) in CIDR notation to match against inbound traffic. There is a limit of 10 IP ranges per rule. A value of '*' matches all IPs (can be used to override the default behavior).`,
 												},
 											},
 										},

website/docs/r/compute_security_policy.html.markdown

@@ -98,7 +98,7 @@ The `match` block supports:
 The `config` block supports:
 
 * `src_ip_ranges` - (Required) Set of IP addresses or ranges (IPV4 or IPV6) in CIDR notation
-    to match against inbound traffic. There is a limit of 5 IP ranges per rule. A value of '\*' matches all IPs
+    to match against inbound traffic. There is a limit of 10 IP ranges per rule. A value of '\*' matches all IPs
     (can be used to override the default behavior).
 
 The `expr` block supports: