Fixed invalid type errors in bbox examples (#27516)

* Update readme.md: Common/stable/2023-06-01

current: Common/stable/2023-07-01
Updated: Common/stable/2023-06-01

* fixed invalid type errors in bbox examples.

* fixed invalid type errors in bbox examples.

* reverted changes

specification/maps/data-plane/Creator/preview/2.0/examples/wfs/WFS_GetFeatures.json

@@ -5,7 +5,12 @@
     "datasetId": "018fda98-e638-0edf-5ef7-28491ff3bed4",
     "collectionId": "unit",
     "limit": 1,
-    "bbox": "-122, 47, -120, 46"
+    "bbox": [
+      -122,
+      47,
+      -120,
+      46
+    ]
   },
   "responses": {
     "200": {

specification/maps/data-plane/Creator/readme.md

@@ -41,9 +41,6 @@ directive:
     from: /specification/maps/data-plane/Creator/preview/2023-07-01-preview
     reason: The files in '/specification/maps/data-plane/Creator/stable/2023-07-01-preview' were never released. Please ignore them, they should not appear in the TOC. '/specification/maps/data-plane/Creator/preview/2023-03-01-preview/' contains the latest preview.
 
-  - suppress: INVALID_TYPE
-    reason: false positive from oav is breaking our example validation. See azure/oav#1020.
-
   - suppress: RESPONSE_SCHEMA_NOT_IN_SPEC
     reason: false positive from oav is breaking our example validation. See azure/oav#1021.
 ```

specification/maps/data-plane/readme.md

@@ -43,9 +43,6 @@ directive:
     where: $.paths["/providers/Microsoft.Subscription/subscriptionOperations/{operationId}"].get
     reason: The reason for this suppression is the API is already released and introducing new LRO properties will not function and are not supported today and will only be developed for the next version of this API.
 
-  - suppress: INVALID_TYPE
-    reason: false positive from oav is breaking our example validation. See azure/oav#1020.
-
   - suppress: RESPONSE_SCHEMA_NOT_IN_SPEC
     reason: false positive from oav is breaking our example validation. See azure/oav#1021.