Utilize annotations

[Maxim-Mazurok]

In order for a parameter to be non-undefined it has to have "required": true property. For example, VideoResource.rate has id: string and rating: string because both of them have required: true in the schema:

/*...*/
"rate": {
  "path": "youtube/v3/videos/rate",
  "parameters": {
    "id": {
      "required": true,
      "type": "string",
      "location": "query"
    },
    "rating": {
      "required": true,
      "type": "string",
/*...*/

However if we take a look at the `id` from `Video`, we'll notice `"annotations"`:
```json5
/*...*/
"id": {
  "type": "string",
  "description": "The ID that YouTube uses to uniquely identify the video.",
  "annotations": {
    "required": ["youtube.videos.update"]
  }
},
/*...*/

We could probably get some use of it, but it'll probably require creating a separate interface for that method... Or using something like Video & Required<Pick<Video, "id">>. I'll create an issue to look into this, but it likely won't help in your case anyway because there are no annotations for list method.

Originally posted by @Maxim-Mazurok in #800 (comment)