Programming a CbrainTask should involve providing a default Tool and ToolConfig

[prioux]

Programmers developing a new CbrainTask do so in a context completely devoid of information about the Tool object and ToolConfig object that the sysadmins are expected to create. That is fine. However, the poor sysadmin has to know quite a bit about the task in order to create that Tool and ToolConfig using the interface.

I suggest that as part of writing and publishing a CbrainTask, the task's programmer be made to
incorporate a set of default values for a Tool object and a first ToolConfig. Maybe embedded within
the PortalTask class? Those values would be supplied as template to the sysadmin when configuring these two things with the interface.

[prioux]

This would be useful within Boutiques-enabled tools too.

[ttaa9]

Was that not essentially turned off for Boutiques (except when docker is present) in #389 and #390?

[prioux]

Oh, maybe. But adding the convention within standard CBRAIN tasks is still a useful thing.