Optionally add task to subset name

[mkolar]

We are currently adding task name to subset name only for renders, to make sure we prevent any overwriting and mixing up. While modelling subset will look like this modelMain, modelBroken , modelHires; published renders look like this renderLighitngMain, renderLightingBG , renderCompositingMain,

From user feedback it is clear that there are more scenarios where embedding task name into a subset is desirable so we should allow for this behaviour across the board, rather than treating renders as something speciall.

Proposal
Add new option to settings when the user could map which families should have task added to the subset name automatically
This needs to be filterable based on host, task, family for now.

Ideally we should also make it possible to choose whether to fill in Task name, task type or task short code, considering we can work with them now.

[mkolar]

Maybe we could make work the same as anatomy, using the same keys to define subset names for various families.

Example, where userInput is taken from the user filled subset name in the creator

"subsets":
    "render": "{family}{task[code]}{userInput}"
    "animation": "{family}{task[type]}{userInput}"
    "image": "{family}{task[name]}{userInput}"

another studio might want to remove the family from the name altogether, which would effectively allow switching to more of a linear, task based workflow.

"subsets":
    "render": "{task[name]}{userInput}"
    "animation": "{task[name]}{userInput}"
    "image": "{task[name]}{userInput}"

[create-issue-branch]

Branch feature/656-optionally-add-task-to-subset-name created!