Move internal terms to ROBOT templates

[jmillanacosta]

The internal terms currently under internal-dev have been robot exported into ROBOT csv templates and divided according to type, and not downstream ontology to be added to. This indication of which ontology the term will be suggested for addition to will be added later, as an annotation, via the same script internal_terms_update.sh (not yet implemented).

The last step will be to use robot template on these template tables to regenerate the internal modules at every build cycle.

Improvements

• Removes the need to handle XML files to add internal terms, tables are used instead
• Standardizes approach and used fields for all internal terms
• Removes the confusion around internal/external modules being named the same way
• The template file names are informative of the type of classes they contain

TBD

• Add annotations to the generated modules (authors, provenance, version IRI...)

• Use robot template to generate the OWLs

• Diff the resulting enanomapper-full.owl ontology to ensure no classes or attributes have been lost