Terminology Design tools integration

[Ca5e]

I've compared the changes in my fork to the master branch instead of the use-tev2 branch as I saw some work already being done on removing TEv1 documentation within the master branch.
Although deployment is done quite differently compared to before, I believe these changes should work with the current setup of the framework repository. My deployment (fork) can be seen here https://ca5e.github.io/framework/docs/essifLab.

[RieksJ]

Changes seem ok.
What should be blocking for merge is that we do not yet have a HRG generated, so merging it to the eSSIF-Lab repo would mean that people browsing the site would no longer see a glossary. So we should wait until either we have a version of the glossary that we can use and publish from the repo, or there is an HRGT that would generate one.

[Ca5e]

I've added the first version of the HRGT to my fork. Please have a look https://ca5e.github.io/framework/docs/essifLab-glossary. Merging should be possible.

[RieksJ]

I have modified the MRGRef tag spec to reflect that converter="<converter>" is optional. Of course, if it is omitted, that would imply that it be specified either on the command-line or in the configuration file (as is currently done). It gets rid of the 'ugly' converter="" text.

[Ca5e]

I think it may be useful to keep a simplified version as the default for using essiflab as the converter value.

So when using {% hrg="" converter="essiflab" %}.
We get:

### [{{glossaryTerm}}]({{navurl}})\n
{{glossaryText}}\n

Instead of the more complex converter that's actually used:

### [{{#if glossaryTerm}}{{glossaryTerm}}{{else}}{{capFirst term}}{{/if}}]({{localize navurl}})\n
{{#if glossaryText}}{{glossaryText}}{{else}}no `glossaryText` was specified for this entry.{{/if}}\n

This relates to writing the documentation for the HRGT and giving certain converter examples mainly. I suspect it might be more user friendly if we keep the essiflab default simple and explain the more complex one separately.

[RieksJ]

Ok to keep simple stuff in the tev2-specifications, but it may help them there to see examples from 'real life'.

[RieksJ]

Please make sure that when texts are encountered that would not work, they somehow get logged with messages that help curators to fix the problem. (I cannot tell whether or not they currently are).