Missing response_metadata and its next_cursor property in users.list response schema

[pyrech]

Description

It looks like the /users.list response miss the definition of the object response_metadata and its next_cursor property.

FYI, the property is mentionned in the openapi example and in the official API documentation. To fix this, you probably only need to add this definition in the schema (inspired from next_cursor defintion in other endpoints):

 "response_metadata": {
    "properties": {
        "next_cursor": {
            "type": "string",
            "x-examples": [
                "dXNlcjpVMEc5V0ZYTlo="
            ]
        }
    },
    "required": [
        "next_cursor"
    ],
    "type": "object"
}

What type of issue is this? (place an x in one of the [ ])

• [x] bug
• [ ] enhancement (feature request)
• [ ] question
• [ ] documentation related
• [ ] testing related
• [ ] discussion

Requirements (place an x in each of the [ ])

• [x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
• [x] I've read and agree to the Code of Conduct.
• [x] I've searched for any related issues and avoided creating a duplicate issue.