Only warn about unmatched inputs in modules

We used to issue an error when the module service's run() method
was called with inputs that are not specified explicitly in the
corresponding ModuleInfo.

That is fragile: should the implementing classes be modified and remove
an input parameter, we should still do our best to continue.

Therefore, let's just warn instead and continue, making the unmatched
input available to the module and just skipping the conversion to
an explicit type (because the info does not specify it).

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Support implicit input parameters in modules

It is sometimes important to support parameters that have not been
specified explicitly by the module, e.g. in ImageJ 1.x macros, where we
need to be able to set the macro options as an engine-specific setting
because the SciJava script service runs scripts on threads different
from the caller's and ImageJ 1.x cannot handle that properly without
some handholding.

This change introduces a special class of settings: input map
entries whose key starts with a dot (e.g. .macroOptions) are considered
implicit, i.e.  no errors about "no such parameter" will be produced.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>