Add scopes as required field of OAuth Flow Object

This makes metaschema consistent with the 3.0.x spec.

Refs #2666

Author: char0n

schemas/v3.0/schema.json

@@ -1489,7 +1489,8 @@
     "PasswordOAuthFlow": {
       "type": "object",
       "required": [
-        "tokenUrl"
+        "tokenUrl",
+        "scopes"
       ],
       "properties": {
         "tokenUrl": {
@@ -1516,7 +1517,8 @@
     "ClientCredentialsFlow": {
       "type": "object",
       "required": [
-        "tokenUrl"
+        "tokenUrl",
+        "scopes"
       ],
       "properties": {
         "tokenUrl": {
@@ -1544,7 +1546,8 @@
       "type": "object",
       "required": [
         "authorizationUrl",
-        "tokenUrl"
+        "tokenUrl",
+        "scopes"
       ],
       "properties": {
         "authorizationUrl": {

schemas/v3.0/schema.yaml

@@ -892,6 +892,7 @@ definitions:
     type: object
     required:
       - tokenUrl
+      - scopes
     properties:
       tokenUrl:
         type: string
@@ -911,6 +912,7 @@ definitions:
     type: object
     required:
       - tokenUrl
+      - scopes
     properties:
       tokenUrl:
         type: string
@@ -931,6 +933,7 @@ definitions:
     required:
       - authorizationUrl
       - tokenUrl
+      - scopes
     properties:
       authorizationUrl:
         type: string