fix(youtube/return-youtube-dislikes): fix temporarily frozen video after opening a shorts

[LisoUseInAIKyrios]

Changed the Shorts patch code to function asynchronously.

This fixes the occasional issue of shorts video being temporarily frozen while the RYD api call completes (it's most noticeable on the first Shorts opened from a cold app start).

This PR also fixes an issue of dislikes not showing if the short was previously disliked.

Integration changes

[LisoUseInAIKyrios]

I added an additional RYD option to turn on/off dislikes for shorts. By default RYD for shorts is turned on.

I figured since the shorts loading is now asynchronously, some users may not like the way the dislikes 'pop' on screen after the video is already playing. It's only a few lines of code to support the option.

I spent way too much time trying to fix the occasional issue of when flipping thru shorts and a new short is swiped on screen, sometimes the prior shorts dislikes is shown for a few milliseconds before updating to the correct value. It's caused by the shorts hook running before the video id hook (so to the RYD patch, it initially applies the dislikes of the prior video).

I see only two reliable ways to fix the occasional flickering shorts dislikes

• Find a different video id hook that always runs before the shorts dislikes components are created (a lot of work to fix this cosmetic issue)
• Modify the existing RYD shorts patch, and also pass in the video id the shorts button belongs to. I can see the video id is a parameter to the patched shorts method, but the video id is buried 2 levels deep inside a data object that has no distinct fingerprints.

I looked for an alternate patch point further outside where the Shorts button is created, but everywhere used the same obfuscated data object and was worse than the current patch location.

On the upside, the image lag (the entire reason I made this PR) is now fixed. Also fixed is the bug where shorts would sometimes show the wrong dislike value (caused by the hooks being called out of order, described above).

[oSumAtrIX]

Find a different video id hook

The earliest good hook is when the server response is parsed to a model. This is known already. That model contains a string field that stores the responded video id and is the earliest hook after parsing the model. The model class is called PlayerResponseModelImpl. I may be wrong, but I concluded this from static analysis.