Netflix does not work due to Widevine Content Decryption Module error in brave://components

[btlechowski]

Follow up to #4646

We do not recover gracefully when Widevine Content Decryption Module fails to download.
Browser needs to be restarted to trigger the update.

Steps to Reproduce

1. Clean profile
2. Navigate to netflix.com and login.
3. Make Widevine Content Decryption Module fail to download (TODO: Determine how)
4. Open brave://components and check Widevine Content Decryption Module status
5. Stream a video

Actual result:

Widevine Content Decryption Module error and the module stays at version 0.0.0.0

Netflix does not play. Shows error.

Expected result:

Widevine Content Decryption Module is downloaded
netflix is playing

Reproduces how often:

10% repro rate

Brave version (brave://version info)

Brave	1.8.36 Chromium: 81.0.4044.69 (Official Build) nightly (64-bit)
Revision	6813546031a4bc83f717a2ef7cd4ac6ec1199132-refs/branch-heads/4044@{#776}
OS	Windows 7 Service Pack 1 (Build 7601.24544)

cc @simonhong @brave/legacy_qa @bsclifton

[kjozwiak]

Example of the issue occurring on my Win 10 x64 machine. I can reproduce this about ~80% of the time on my Win 10 x64 machine (not sure why it's so high for me). Refreshing/re-opening Netflix in a new tab doesn't do anything either. As @btlechowski mentioned, it requires a restart to recover most of the time.

[kjozwiak]

Seems like I might have been running into a connectivity issue when attempting to download the Widevine component for the first time on a new profile. I tried the same test case last night ~11pm EST and it worked fine without any issues. I tried it 10 times and didn't run into any of the above.

We should look into a way of retrying the component download if it fails on the first attempt on a new profile. This might hurt retention as users might think Netflix and other streaming services don't work if they run into the above the first time they enable it on a new profile. However, it resolves itself when you restart the browser.

[rebron]

Note that we want to generalize this for all components to do a re-try logic to check for component updates without requiring a browser restart.