Correct ResourceQuota PriorityClass config example (#12055)

The LimitedResource type has the field "MatchScopes" as a sibling to
the field "Resource," but the YAML document in the example showed the
"MatchScopes" field as a child of the top-level Configuration
type. Correct the example to match the actual schema.

While we're here, swap the order of the "scopeName" and "operator"
fields used in the YAML, to make it clearer in infix style that the
operator binds the scope name to a (possibly empty) set of values.

content/en/docs/concepts/policy/resource-quotas.md

@@ -551,10 +551,10 @@ plugins:
     kind: Configuration
     limitedResources:
     - resource: pods
-    matchScopes:
-    - operator : In
-      scopeName: PriorityClass
-      values: ["cluster-services"]
+      matchScopes:
+      - scopeName: PriorityClass 
+        operator: In
+        values: ["cluster-services"]
 ```
 
 Now, "cluster-services" pods will be allowed in only those namespaces where a quota object with a matching `scopeSelector` is present.
@@ -562,8 +562,8 @@ For example:
 ```yaml
     scopeSelector:
       matchExpressions:
-      - operator : In
-        scopeName: PriorityClass
+      - scopeName: PriorityClass
+        operator: In
         values: ["cluster-services"]
 ```