Mark ContextLost_WebGLBlockedAfterJSNavigation flaky on Win NVIDIA

TBR=kbr

Bug: 965268
Change-Id: I1984c7f7ffe81f5e673c9f7427d31b81c78b4a74
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1797651Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#695637}

content/test/gpu/gpu_tests/test_expectations/context_lost_expectations.txt

-# tags: [ android linux lion mac mountainlion win win7 win8 ]
+# tags: [ android linux lion mac mountainlion win win7 win8 win10]
 # tags: [ debug ]
 # tags: [ amd-0x6779 nvidia qualcomm-adreno-(tm)-418 qualcomm-adreno-(tm)-420 ]
 # tags: [ asan no-asan ]
@@ -13,6 +13,9 @@ crbug.com/603329 [ win7 ] ContextLost_WebGLContextLostFromGPUProcessExit [ Retry
 # Win8 Release and Debug NVIDIA bots.
 crbug.com/524808 [ win8 nvidia ] ContextLost_WebGLContextLostFromSelectElement [ Skip ]
 
+# Win10 NVIDIA
+crbug.com/965268 [ win10 nvidia ] ContextLost_WebGLBlockedAfterJSNavigation [ RetryOnFailure ]
+
 # Flakily timing out on Win x64 Debug bot. Unfortunately we can't identify this
 # separately from the 32-bit bots. Also unfortunately, the flaky retry mechanism
 # doesn't work well in this harness if the test times out. Skip it on this