feat: OpenAPI: Fix nova examples (#1312)

When generating the nova AZ detail schema we are adding examples to the
`hosts` object, but we are doing it wrong:

- We are adding a dictionary instead of a list, which is what the plural
  form of example indicates and also what we can see in the OpenAPI spec
  documentation [1].

- The contents of the example are wrong, it shouldn't have the `JSON
  request` key, as we can see in the upstream docs [2].

This patch fixes the examples to be correct.

[1]: https://swagger.io/specification/#model-with-example
[2]: https://docs.openstack.org/api-ref/compute/#get-detailed-availability-zone-information

Change-Id: Ic694ee083f55d44d0ecdb8a72561e24ec1b70583

Changes are triggered by https://review.opendev.org/951884

Author: gtema

openstack_types/data/compute/v2.100.yaml

@@ -11634,8 +11634,7 @@ components:
                   of host and service objects. The service object returns three parameters representing
                   the states of the service: `active`, `available`, and `updated_at`.
                 examples:
-                  JSON request:
-                    conductor:
+                  - conductor:
                       nova-conductor:
                         active: true
                         available: true

openstack_types/data/compute/v2.yaml

@@ -11634,8 +11634,7 @@ components:
                   of host and service objects. The service object returns three parameters representing
                   the states of the service: `active`, `available`, and `updated_at`.
                 examples:
-                  JSON request:
-                    conductor:
+                  - conductor:
                       nova-conductor:
                         active: true
                         available: true