Simplify complex options

[tdudgeon]

We are starting to create jobs that have a complex set of options.
Complex in that there can be a lot of them, and complex in that there can be a lot of duplication between jobs.
This issue is primarily to address the former, but bear in mind that the latter is also being discussed, though is presumably primarily a job definition problem.

We need to explore approaches that can simplify the display of options to the user. Two obvious solutions come to mind:

1. introduce the concept of basic and advanced options. Basic ones would be displayed by default, but advanced ones (that will rarely be used) can be displayed if requested by the user. Implicit in this is that advanced options will always have default values and never be mandatory.
2. Introduce the concept of categories of options. This doesn't reduce the complexity, but does allow it to be more understandable. One might expect it to be possible to show/hide an individual category of options.

@OliverDudgeon can you have a think about what is possible with the jsonforms library?

[OliverDudgeon]

Easiest way feels like there would be separate schemas for the basic and advanced options. The basic would be displayed like we do currently, but the advanced ones would be hidden behind a button click.

Another potential way to do this that shouldn't require any extra work is to use the dependencies functionality in the schema. This would allow us to nest a number of fields inside a tickbox ("enable advanced options").

[tdudgeon]

The former seems unworkable due to extra maintenance and lack of flexibility.

The latter looks much more interesting. I like that if I specify to have pets then each person then has options added about their pets (but then when I revisited the pages it didn't behave well).
Haven't looked at how this works, but it seems promising.

[tdudgeon]

Ollie suggests that this example can be used for standard vs. advanced options.