Remove EXT:crawler hint, because it is not a problem anymore

Classes/Controller/BackendController.php

@@ -86,7 +86,6 @@ public function supportAction(): ResponseInterface
             'foundHtaccess' => $htaccessConfigurationService->foundConfigurationInHtaccess(),
             'htaccessPaths' => $htaccessConfigurationService->getHtaccessPaths(),
             'missingModules' => $htaccessConfigurationService->getMissingApacheModules(),
-            'useCrawler' => ExtensionManagementUtility::isLoaded('crawler'),
             'envInfoLink' => $environmentService->getLink(),
             'envInfoMarkdown' => $environmentService->getMarkdown(),
         ];

Resources/Private/Templates/Backend/Support.html

@@ -38,15 +38,6 @@ <h2>Configuration Test</h2>
 		</f:else>
 	</f:if>
 
-	<f:if condition="{useCrawler}">
-		<f:then>
-			<div class="alert alert-warning" role="alert">You are using EXT:crawler. Please check this issue if there are problems with wrong page contents in the cache: https://github.com/lochmueller/staticfilecache/issues/260</div>
-		</f:then>
-		<f:else>
-			<div class="alert alert-info" role="alert">You don't use crawler. EXT:crawler could result in some useless cache entries: https://github.com/lochmueller/staticfilecache/issues/260</div>
-		</f:else>
-	</f:if>
-
 	<h2>Support the extension development...</h2>
 	<p>
 		<a href="https://www.paypal.me/lochmueller/100" target="_blank" class="btn btn-success">

composer.json

@@ -57,9 +57,6 @@
 		"lochmueller/seocli": "Scan websites against SEO criteria and/or trigger the indexing process and cache warming in deployment scripts",
 		"friendsofsymfony/http-cache": "For HTTP proxy cache services like Varnish"
 	},
-	"conflict": {
-		"tomasnorre/crawler": "<11.0.1"
-	},
 	"config": {
 		"vendor-dir": ".Build/vendor",
 		"bin-dir": ".Build/bin",