refactor(extractors): simplify and combine jwplayer extraction

[Bnyro]

I noticed that a lot of extractors are based on the following pattern:

1. Do some magic to obtain a script file containing JWPlayer config
2. Extract stream URLs from this JWPlayer config

Previously, all extractors had their own logic for extracting the JWPlayer config, even though the JavaScript data parsed always looks the same. So there's been a lot of duplicated code that behaved inconsistent (i.e. some only supported m3u8 links and no other stream types like mp4 and others didn't parse the subtitles).

This logic is now handled by JWPlayerHelper.kt.

I've also noticed that some of the files could be merged, e.g.

• Filemoon
• Filesim
• Streamwish

contain almost the exact same logic and

• Gamovideo
• Hxfile
• Supervideo
• Vtbe
• Vidhide

also do the exact same thing. I suspect that all these providers are based on the exact same code (only some UI changes), but I haven't moved their extractors into the same class yet because I'd like to hear some other opinions first before doing that.

The deleted files are usages of the JWPlayer API on sites that no longer exist, so I removed them.

[okibcn]

I am reworking some extractors. I recently fixed Vidmoly that would benefit from this utility as it fits in the same class of jwplayer config string.

On the other hand you mention Filemoon, but it is no longer working since now the load of the iframe page is way more complicated and behind several scripts.

[Bnyro]

On the other hand you mention Filemoon, but it is no longer working since now the load of the iframe page is way more complicated and behind several scripts.

Yes, true. I only noticed that Streamwish, Filesim and Filemoon use almost the same code, so it's possible that they're all the same provider (i.e. the same company hosting it), that note is not meant to be related to JwPlayer.