Remove unnecessary cache clear in Views tests

Views access plugins alter route's access requirements, altered routes must have associated cache tags, because site builders can modify the view (the config entity), causing different access alterations. Unless the responses for this route always have corresponding cache tags (i.e. the View config entity), it is possible for access to be denied once to the anonymous user, and then for the resulting page to be cached forever. The View config entity's cache tag does not get set because the route's controller is never executed, because access checking happens at the routing level, not at the controller level.

Quoting the patch in #606840: Enable internal page cache by default:

diff --git a/core/modules/views/src/Tests/Plugin/AccessTest.php b/core/modules/views/src/Tests/Plugin/AccessTest.php
index 4bc77db..c756706 100644
--- a/core/modules/views/src/Tests/Plugin/AccessTest.php
+++ b/core/modules/views/src/Tests/Plugin/AccessTest.php
@@ -7,6 +7,7 @@
 
 namespace Drupal\views\Tests\Plugin;
 
+use Drupal\Core\Cache\Cache;
 use Drupal\views\Tests\ViewTestData;
 use Drupal\views\Views;
 
@@ -101,6 +102,13 @@ function testStaticAccessPlugin() {
     // termination event fires. Simulate that here.
     $this->container->get('router.builder')->rebuildIfNeeded();
 
+    // Clear the page cache.
+    // @todo Remove this. The root cause is that the access plugins alters the
+    //   route's access requirements. That means that the 403 from above does
+    //   not have any cache tags, so modifying the View entity does not cause
+    //   the cached 403 page to be invalidated.
+    Cache::invalidateTags(['rendered']);
+
     $this->assertTrue($access_plugin->access($this->normalUser));
 
     $this->drupalGet('test_access_static');