WIP: Demonstrate Hierarchy Functions

[etimr]

Provides an example of an hierarchy function as ListReport and ValueHelp

• currently only READ
• only on HANA

Changes:

• LineItem parent.name is removed from app/common.cds, because it leads to OData requests with $expand for an hierarchy function which are not supported yet
• sap.common.CodeList aspect was removed from Genres entity because it provides ValueHelp dialog implicitly through annotation @cds.odata.valuelist. It also uses the annotation @cds.autoexpose, because of this entity Genres should be exposed explicitly in CatalogService and ReviewService after sap.common.CodeList is removed.
• renaming in the view GenreHierarchy is temporal and will be solved by CAP Java team in the future

  node   as node_id,
  parent_node as parent_id

• to enable tree tables as ListReport add to manifest.json:

  "tableSettings": {
   "type": "TreeTable",
   "hierarchyQualifier": "NodesHierarchy",
  ...
  }

• to enable tree table for ValueHelp hierarchical entity should be annotated with PresentationVariant and root entity with PresentationVariantQualifier

[cla-assistant[bot]]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

:white_check_mark: etimr
:x: OlenaTi
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cla-assistant[bot]]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}