perf(DRM): pass preferredKeySystems to filterManifest()

[tykus160]

Follow up to #5391
Always use preferredKeySystems during manifest filtering, not only via DRM Engine.

[shaka-bot]

Incremental code coverage: 100.00%

[joeyparrish]

I see the "perf" label... Do you have any rough data on how much of a performance improvement this is?

[tykus160]

@joeyparrish previous PR reduced load i.e. on Xbox Series S from ~400 ms to ~100 ms as it avoided 10 calls to widevine. This one does relatively the same, but on manifest updates.

[avelad]

@tykus160 Since Xbox only supports PlayReady, I wonder if, given this improvement, we should add the default PlayReady drm.preferredKeySystems config for Xbox. What do you think?

[tykus160]

@avelad recently shaka added some platform-dependant logic, so I'd say adding by default preferredKeySystems for single DRM platforms makes sense in current state (assuming we don't care about ClearKey).
It would be:

• PlayReady for Xbox
• Widevine for Chrome (*) & Firefox
• Fairplay for Safari

* Chrome is tricky though, as Chromium-based platforms would be also affected, i.e. Platform.isChrome() returns true for WebOS which also supports PlayReady.

[avelad]

ClearKey it's necessary, so, for me the platforms are Xbox and PlayStation since only supports PlayReady .

ClearKey support will eventually come to Safari, so I don't want to limit the platform.