Moving some descriptions or description parts to infoText to simplify the json-editor form interface

- Make the goals object an array of fields instead, to better compare with templates schema
- Improve documentation, for use with json-editor

* translation field info now includes field validity (because it is no longer redundant with field output)
* the TemplateField's translate method now always returns an unvalidated field output, with the separate "valid" property indicating whether it is valid or not
* the TemplateField's validate method now returns a boolean, rather than a validated output

* make "domain" the only required parameter
* make all other parameters optional and named
* use default fallback template definition
* allow changing the force-required fields

* make "domain" the only required parameter
* make all other parameters optional and named
* use default fallback template definition
* allow changing the force-required fields

* domain configuration revision cache now stores content revisions instead of (parsed) configuration revisions
* parsing of revision content now occurs later, at revision loading, rather than at revision fetching
* template, field and procedure constructors now have a "strict" option which if set to false ignores individual invalid elements (fields, procedures and steps, respectively)
* TemplateConfiguration implementation of the "parse" method uses the actual constructors to validate definitions

- If one or more capturing groups are defined, do not return full match
- Ignore optional capturing groups not found in the match
- Support capturing groups with global flag