A module action has two parts: One is the actual, headless (that is, without
graphical interface or any other mechanism to capture the necessary parameters) Abstract, and
an optional AbstractVisualAction that in the end, will call the backend action.
Visual actions that are provided by each module (that is, all those actions that are loaded
dynamically and are defined outside the module Navigation) must extend from this class and be
registered at module startup.