fixing PiP / Auto PiP

[raszpl]

• new Option "Auto-PiP only outside source Tab" add an option to auto-close PIP when the source tab active/in focus #1850
• dont Auto PiP paused videos Auto PIP - only works when the video is paused and not when playing, should be the opposite #1352
• adds warning about current Chrome limitations "PiP requires recent User interaction with source page. This is Chrome Picture-in-Picture API limitations and we cant do anything to bypass it. Works best with Autoplay disabled and manual Play control or deliberately clicking somewhere on the page before switching Tabs."
• checks to not throw errors in FF/browsers not supporting Chrome PiP API.
• hiding Auto PiP Options altogether in FF/browsers not supporting Chrome PiP API Auto PIP Not Working #2051
• dont "Auto-pause while I'm not in the tab" if User engaged Chrome PiP manually Picture in Picture pauses on popout when "Auto-pause while I'm not in the tab" is enabled #1907
• dedicated ImprovedTube.enterPip(disable) function for entering/exiting PiP, required to keep everything in sync.
• satus.js modal and linter fixes:

1. satus.components.select dispatches 'render' Event on component.render, fixes updating player_quality by triggering its on.render
2. sections can be functions was breaking modals, make exception
3. modal 'content' can be a function
4. satus.indexOf was always broken
5. satus.getProperty was always broken
6. linter cleanup
7. removing obsolete flash detection

• thrown in Menu player_quality fix, it wasnt showing disabled resolutions correctly

Minus ~24 linter errors, 66 -> 42 .

[ImprovedTube]

4k is the known name. "Message": "2160p - 4K"

https://trends.google.com/trends/explore?date=all&q=4k,2160p,full%20hd,1080p,8k

---

Flash

( https://github.com/ruffle-rs/ruffle ( https://github.com/swf2js/swf2js ) , ( just for fun:
https://trends.google.com/trends/explore?date=all&q=flash,html5,vbscript,actionscript,js lol.) )

[raszpl]

4k is the known name. "Message": "2160p - 4K"

which 4K, DCI 4K is 4096 x one of many choices, like you got 4K DCI full frame 4096 x 2160, 4K DCI Scope 4096 x 1716 etc :] Exact industry name for 16:9 3840 × 2160 as on YT is 4K UHD :) But that wasnt the reason for this change, code works only if all numerical resolution values are directly in player_quality.options with no lookup from messages.json + it makes little sense to keep it in language/messages.json translate tables, its not like 4K has different names in different languages :).
player_quality.render is no longer hardcoded (like previous one at offset 7), can dynamically define cutoff for resolutions painted red, might be handy with qualityWhenRunningOnBattery later on.

This was my favorite type of patch - fixed a bunch of things and its "+220 −218" barely changed size :). Still needs a lot of testing, as Chrome PiP is very fragile not to mention relations between different states arent really simple.

I forgot to switch it to draft when I went for a nap before pushing last changes :] #2458