Enable allowClearForRobustResourceInit for AMD drivers

AMD drivers that have trouble clearing textures have been
blocklisted by Chromium.

Since Intel and NVidia drivers were already been allowed to
clear for robust resource init, we're good to enable it for all IHVs.

Bug: angleproject:4460
Change-Id: If71d01a91806ffc0a78c30f0cc393e105a6c9c74
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2204698
Reviewed-by: Jamie Madill <[email protected]>
Reviewed-by: Geoff Lang <[email protected]>
Commit-Queue: Rafael Cintron <[email protected]>

Author: RafaelCintron

src/libANGLE/renderer/d3d/d3d11/renderer11_utils.cpp

@@ -2466,9 +2466,10 @@ void InitializeFeatures(const Renderer11DeviceCaps &deviceCaps,
     ANGLE_FEATURE_CONDITION(features, selectViewInGeometryShader,
                             !deviceCaps.supportsVpRtIndexWriteFromVertexShader);
 
-    // NVidia drivers have no trouble clearing textures without showing corruption. AMD ones do.
-    // Intel drivers that have trouble have been blocklisted to the DX9 runtime by Chromium.
-    ANGLE_FEATURE_CONDITION(features, allowClearForRobustResourceInit, isNvidia || isIntel);
+    // NVidia drivers have no trouble clearing textures without showing corruption.
+    // Intel and AMD drivers that have trouble have been blocklisted by Chromium. In the case of
+    // Intel, they've been blocklisted to the DX9 runtime.
+    ANGLE_FEATURE_CONDITION(features, allowClearForRobustResourceInit, true);
 
     // Don't translate uniform block to StructuredBuffer on Windows 7 and earlier. This is targeted
     // to work around a bug that fails to allocate ShaderResourceView for StructuredBuffer.