Follow-up to premature #999: there are more places where we pass an empty ocrd_tool around that will never be used.

Reasoning (from ocrd_tesserocr discussion):

That's despite ocrd==2.47.1. Where does the empty ocrd_tool come from???

Aha! It turns out that my #999 was premature: we also pass an unnecessary ocrd_tool in other places:

• run_processor kwarg:

  core/ocrd/ocrd/processor/helpers.py

  Line 38 in cff8dda

  ocrd_tool=None,

• run_processor calling get_processor:

  core/ocrd/ocrd/processor/helpers.py

  Line 91 in cff8dda

  ocrd_tool=ocrd_tool,

• get_processor kwarg:

  core/ocrd/ocrd/processor/helpers.py

  Line 306 in cff8dda

  ocrd_tool: dict = None,

• get_processor calling constructor:

  core/ocrd/ocrd/processor/helpers.py

  Line 325 in cff8dda

  ocrd_tool=ocrd_tool,

Now, the big story here is: none of these places is needed (or used) – neither currently, nor for #974 nor #884!

It's also clear now, why we never used this: you need runtime information (from the CLI) for this. Either we are already on the CLI (Processor CLI decorator in all processor modules) or we have to make foreign CLI calls and parse the JSON response from the concrete Processor subclasses (which don't live in our venv, or we don't know the class name of, or are bashlib anyway).