[YouTube] Add support for premieres in lockupViewModels

[AudricV]

• I carefully read the contribution guidelines and agree to them.
• I have tested the API against NewPipe.

This PR adds support for upcoming premieres in video lockupViewModels. Their structure looks like the following sample for the en-GB interface language (with several fields not different than on regular videos and running livestreams omitted):

Details

{
  "lockupViewModel": {
    "contentImage": {
      "thumbnailViewModel": {
        "image": {},
        "overlays": [
          {
            "thumbnailOverlayBadgeViewModel": {
              "thumbnailBadges": [
                {
                  "thumbnailBadgeViewModel": {
                    "text": "Upcoming",
                    "badgeStyle": "THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT",
                    "animationActivationTargetId": "VIDEO_ID",
                    "animationActivationEntityKey": "REDACTED",
                    "lottieData": {
                      "url": "https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json",
                      "settings": {
                        "loop": true,
                        "autoplay": true
                      }
                    },
                    "animatedText": "Now playing",
                    "animationActivationEntitySelectorType": "THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE"
                  }
                }
              ],
              "position": "THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"
            }
          },
          {
            "thumbnailHoverOverlayToggleActionsViewModel": {
              "buttons": []
            }
          }
        ]
      }
    },
    "metadata": {
      "lockupMetadataViewModel": {
        "title": {
          "content": "VIDEO_TITLE"
        },
        "image": {
          "decoratedAvatarViewModel": {}
        },
        "metadata": {
          "contentMetadataViewModel": {
            "metadataRows": [
              {
                "metadataParts": [
                  {
                    "text": {
                      "content": "VIDEO_CHANNEL_NAME",
                      "styleRuns": [],
                      "attachmentRuns": []
                    }
                  }
                ]
              },
              {
                "metadataParts": [
                  {
                    "text": {
                      "content": "56 waiting"
                    }
                  },
                  {
                    "text": {
                      "content": "Premieres 14/08/2025, 13:00"
                    }
                  }
                ]
              }
            ],
            "delimiter": " • "
          }
        },
        "menuButton": {}
      }
    },
    "contentId": "VIDEO_ID",
    "contentType": "LOCKUP_CONTENT_TYPE_VIDEO"
  }
}

[litetex]

Cool PR. Can we get a test for it? (maybe one that is mock only)

[AudricV]

The issue I see is breaking changes with premieres won't be detected. Free feel to find a way to reliably get them or to add a mock only test :)

[litetex]

A few lines above you write "This approach is language dependent"

I think parsing this might crash on different languages, so maybe add a try catch block here?

[AudricV]

We do not support other localizations than en-GB.

This is still interesting to do a try catch and throw a ParsingException when the date could not be parsed.

[Stypox]

I added a try-catch

[Stypox]

Thank you! I implemented the remaining suggestions, now this looks good to me. In particular:

• I added mock tests, that load the JsonObject from file and pass it to the StreamInfoItemExtractor, and then there are a bunch of assertions checking the returned data. I obtained the JSON data by accessing the YouTube website on my PC.
• I simplified the date handling code, so that getTextualUploadDate() returns the raw textual date as it's supposed to do, instead of first parsing it and then formatting it again. This way even if parsing fails, at least the textual date can act as a fallback.
• I added a try-catch around date parsing as suggested in a review comment.