Implement metadata according to the generic TextAPI

Goal: a reference implementation according to the specs given in the generic TextAPI

Pls refer to: generic TextAPI

TODO:

• remove rendering for x-prefix (project-specific API eXtensions)
• render metadata object provided by the manifest object holding arbitrary, project specific data
• keep item-sections from being rendered if no data is delivered => (cardinality "?" / "*")
• adjust the (global) config options
• update the README accordingly

Decisions to be made:

• should everything be rendered with a cardinality of either "1" and / or "+" (if not, what should be rendered?)
• which metadata fields should be configurable (imho everything with cardiality "1" and / or "+" as far as it is about to being rendered)
• in which order should we display the single fields

Related:

• Provide license information for images
• Provide license information for the text
• Move x- prefixed info to Metadata Object in back end

added to epic subugoe&12

changed milestone to %Ahikar Version 0.16.0

added Ahikar label

assigned to @schneider210

added To Do label

added Metadata label

added TIDO label

added Doing label and removed To Do label

changed title from remove rendering for "x-" to Implement metadata according to the generic TextAPI

changed the description

changed the description

@kvoigt1 I already left you a pm in Rocket.Chat. Let's pls discuss these topics described aboved (e.g. decisions) as soon as it fits for you :-)

removed milestone %Ahikar Version 0.16.0

added waiting for code review label and removed Doing label

marked the checklist item update the README accordingly as completed

marked the checklist item keep item-sections from being rendered if no data is delivered => (cardinality "?" / "*") as completed

mentioned in merge request !115 (merged)

mentioned in commit f90322a9

closed

removed waiting for code review label