Media list endpoints have incorrect OpenAPI (previously Swagger) example definitions

[zackkrida]

Description

Our API uses an OpenAPI schema, which can be viewed here:

https://api.openverse.org/v1/schema/?format=json (exclude the format param for yaml)

The examples for the /v1/audio/ and /v1/images/ paths are incorrect. This might be easiest to view locally like so:

http https://api.openverse.org/v1/schema/\?format\=json | jq '.paths."/v1/images/".get.responses."200".content."application/json".examples.OK'

{
  "result_count": 10000,
  "page_count": 20,
  "page_size": 20,
  "page": 1,
  "results": [
    {
      "result_count": 1, // See incorrectly duplicated, nested properties here
      "page_count": 1,
      "page_size": 20,
      "page": 1,
      "results": [
        {
          "id": "4bc43a04-ef46-4544-a0c1-63c63f56e276",
          "title": "Tree Bark Photo",
          "indexed_on": "2022-08-27T17:39:48Z",
		  ...

You'll see a similar result for the audio path at http https://api.openverse.org/v1/schema/\?format\=json | jq '.paths."/v1/audio/".get.responses."200".content."application/json".examples.OK'

As you can see, the results array is incorrectly nested. This is problematic because various codegen tools, API consumers, and so on rely on this spec for their own work, and inaccurate examples could prevent code generation and/or give false impressions of the workings of the API.

Additional context