FYI: rebased PR's branch (82 commits)

Can we please force merge (review) of this PR? .. beside the bugfix in the second commit, the modularization and documentation from the first commit is a prerequisite for further development of the response types / thanks!

FYI rebased (0a11478 --> 7a48dc7) to solve conflict with current master.

After a long thinking, I'm "meh" about this PR:

• why not use the TypedDict instead of documentation? I prefer code as documentation rather documentation that might get out of sync. We even imagine to have some dedicated classes ( here a prototype )
• most of the functions inside the new modules could be methods (some as class methods). For example is_answer ... could be a static method, so it is super easy to add a new result type (see query.py and see line 241).
• why "standard" result are not in a new module?
• why not split this PR in two:
  • one to fix the hostname_replace on infoboxes
  • one where we take time to rewrite results.py
    ?

why not use the TypedDict instead of documentation? I prefer code as documentation

This is often what I hear .. but it fails in two ways ..

• first, what when the code has a bug .. by saying the code is the documentation no one can check whats going wrong in the function.

• how can code document the relation of objects to each other when the code uses ellipses / where is the "Interface" description of the result-types on which a UI developer can build up UI interface (HTML templates).

We have a templates .. these templates are undocumented, split up in files and macros .. and we have multiple result types .. how should a newbie understand all this? .. I toked me a week ore more to find all the relations and to write it down .. IMO the lack of so many needed documentation is the reason why this project is so hard to get into .. to be honest, several of your implementations I don't understand because there is no documentation .. that is why I ask dump questions like the one today #1559 .. just one small hint in a docstring of the method of the abstract class about what the meaning is of returning None is needed to save a lot of time and make things clear.

rather documentation that might get out of sync.

IDK a better way to document, the doc-strings are in the source code, a few lines above the code that implements what the doc-string described .. compile the docs make docs.live and open http://0.0.0.0:8000/src/searx.results.html to see what I mean.