Reload active tab when widevine library is ready to use

[simonhong]

Resolves brave/brave-browser#4646

Submitter Checklist:

• Submitted a ticket for my issue if one did not already exist.
• Used Github auto-closing keywords in the commit message.
• Added/updated tests for this change (for new code or code which already has tests).
• Verified that these changes build without errors on
  • Android
  • iOS
  • Linux
  • macOS
  • Windows
• Verified that these changes pass automated tests (unit, browser, security tests) on
  • iOS
  • Linux
  • macOS
  • Windows
• Verified that all lint errors/warnings are resolved (npm run lint)
• Ran git rebase master (if needed).
• Ran git rebase -i to squash commits (if needed).
• Tagged reviewers and labelled the pull request as needed.
• Request a security/privacy review as needed.
• Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone
• Public documentation has been updated as necessary. For instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protection-Mode
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Custom-Headers
  • https://github.com/brave/brave-browser/wiki/Web-compatibility-issues-with-tracking-protection
  • https://github.com/brave/brave-browser/wiki/QA-Guide

Test Plan:

See STR in issue

Reviewer Checklist:

• New files have MPL-2.0 license header.
• Request a security/privacy review as needed.
• Adequate test coverage exists to prevent regressions
• Verify test plan is specified in PR before merging to source

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on.
• All relevant documentation has been updated.

[simonhong]

Merged because only test-security test was failed.

[kjozwiak]

@simonhong I don't think this is working 100% and is still reproducible. Went through the above change with the following builds:

Brave | 1.8.40 Chromium: 81.0.4044.69 (Official Build) nightly (64-bit)
-- | --
Revision | 6813546031a4bc83f717a2ef7cd4ac6ec1199132-refs/branch-heads/4044@{#776}
OS | macOS Version 10.15.3 (Build 19D76)

Brave | 1.8.40 Chromium: 81.0.4044.69 (Official Build) nightly (64-bit)
-- | --
Revision | 6813546031a4bc83f717a2ef7cd4ac6ec1199132-refs/branch-heads/4044@{#776}
OS | Windows 10 OS Version 1909 (Build 18363.720)

Looks like the Pardon the interruption error which mentions that the component needs to be updated is still appearing as per the following:

With macOS, you'll still get the above message but the page will eventually refresh automatically and start playing the content as per the following example:

However, on Win 10 x64, it doesn't automatically fresh the page and the above Pardon the interruption error is visible even after refreshing several times. You'll basically need to restart Brave to get Netflix working. Example:

@btlechowski also ran into the above issues on Windows but I'll let him comment 👍

@simonhong @bsclifton this PR seems to improve macOS but it still seems to be broken on Windows. As brave/brave-browser#4646 is labelled as Win specific, it doesn't improve the situation on Win.

[btlechowski]

On Windowis, the original issue brave/brave-browser#4646 (comment) mentions that page reload fixed the issue. This is not the case with the issue @kjozwiak and I are seeing as reload does not fix the issue.
I noticed that the widevine component fails to download.
I logged brave/brave-browser#8862.