[mod] drop SearXNG's checker (#5767)

To date, there is no analysis for the checker that could be evaluated in any
meaningful way.

- https://github.com/searxng/searxng/issues/3407
- https://github.com/searxng/searxng/pull/3312

The checker would need to be completely redesigned, but even then, its
usefulness and the maintenance required for it would be disproportionate.

TBH: In its current form, it is useless and only consumes resources and
causes the engines to be blocked, because these tests (query terms) come
from *hundreds* of instances and could be interpreted as bot attacks.

Related issues: [search.checker](https://github.com/searxng/searxng/issues?q=label%3A%22search.checker%22)

Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>

searx/templates/simple/stats.html

@@ -124,23 +124,6 @@
                 {% endif %}
             {% endfor %}
         {% endfor %}
-        {% if engine_reliabilities[selected_engine_name].checker %}
-            <h3>{{ _('Checker') }}</h3>
-            <table>
-                <tr>
-                    <th scope="col" class="failed-test">{{ _('Failed test') }}</th>
-                    <th scope="col">{{ _('Comment(s)') }}</th>
-                </tr>
-                {% for test_name, results in engine_reliabilities[selected_engine_name].checker.items() %}
-                <tr>
-                    <td>{{ test_name }}</td>
-                    <td>
-                        {% for r in results %}<p>{{ r }}</p>{% endfor %}
-                    </td>
-                </tr>
-                {% endfor %}
-            </table>
-        {% endif %}
         {{ new_issue(selected_engine_name, engine_reliabilities[selected_engine_name]) }}
     </div>
 {% endif %}