Is there an existing issue for this?

• I have searched the existing issues

Please describe the new behavior that that will improve Egeria

egeria-ui-components build is created in the dist/ folder.
For the moment is pushed in the main branch with PR.
Create a github workflow that builds egeria-ui-components and publish the dist folder.

@planetf1 sugested to investigate:
Github packages also offer a repo - for containers, gems, npm, maven, gradle, nuget - not explored but all there.

Tasks in order

• Entity Type inheritance
  • hard code the nodes and edges
  • display new happy graph with hard coded data - should entity type properties in node
  • Show extended entity type properties , attributes , classifications and relationships
  • issue the rest calls to get the data from the server
• Entity type centric graph
  • hard code the nodes and edges
  • display new happy graph with hard coded data - should entity type properties in node
  • Show extended relationship properties , entity type properties , attributes , classifications and relationships
• Add boolean filters, enterprise , deprecation
• Add filters from dropdown
• Add ability to display a type from a guid