[refactor] unit tests to utilize paramaterized and break down monolithic tests

- for tests which perform the same arrange/act/assert pattern but with different
  data, the data portion has been moved to the ``paramaterized.expand`` fields

- for monolithic tests which performed multiple arrange/act/asserts,
  they have been broken up into different unit tests.

- when possible, change generic assert statements to more concise
  asserts (i.e. ``assertIsNone``)

This work ultimately is focused on creating smaller and more concise tests.
While paramaterized may make adding new configurations for existing tests
easier, that is just a beneficial side effect.  The main benefit is that smaller
tests are easier to reason about, meaning they are easier to debug when they
start failing.  This improves the developer experience in debugging what went
wrong when refactoring the project.

Total number of tests went from 192 -> 259; or, broke apart larger tests into 69
more concise ones.

tests/unit/test_answerers.py

@@ -2,15 +2,16 @@
 # pylint: disable=missing-module-docstring
 
 from mock import Mock
+from parameterized import parameterized
 
 from searx.answerers import answerers
 from tests import SearxTestCase
 
 
 class AnswererTest(SearxTestCase):  # pylint: disable=missing-class-docstring
-    def test_unicode_input(self):
+    @parameterized.expand(answerers)
+    def test_unicode_input(self, answerer):
         query = Mock()
         unicode_payload = 'árvíztűrő tükörfúrógép'
-        for answerer in answerers:
-            query.query = '{} {}'.format(answerer.keywords[0], unicode_payload)
-            self.assertTrue(isinstance(answerer.answer(query), list))
+        query.query = '{} {}'.format(answerer.keywords[0], unicode_payload)
+        self.assertIsInstance(answerer.answer(query), list)