Re-architecture of the hypergraph-cli tool/typesync functionality

[cmwhited]

Description

Comes out of proposal outlined in #348

Blocked by #351

The hypergraph-cli/TypeSync tool currently lets the user create, edit and manage multiple hypergraph-enabled apps in one place.

This change would be to instead make the hypergraph-cli be contextualized to the current hypergraph-enabled repo that it is being ran inside of.
This allows the removal of a datastorage mechanism (currently sqlite that has to run on the users machine) to store the users app and greatly simplifies the work being done by the hypergraph-cli and the TypeSync tool to focus on managing a single schema/mapping.

Tasks

• Remove database code paths and logic from the cli tool exposed api
  • Done in feat(#352 typesync.v2 | cli): buildout a CLI from the hypergraph package to read schema/mapping files #418
• On init, introspect the repo/directory where the cli tool is running; look for an existing schema.ts file
  • Done in feat(#352 typesync.v2 | cli): buildout a CLI from the hypergraph package to read schema/mapping files #418
• Introspect the schema.ts and build a stream of the types/properties from the schema
  • Done in feat(#352 typesync.v2 | cli): buildout a CLI from the hypergraph package to read schema/mapping files #418
• When the hypergraph typesync command is called, open the TypeSync studio app that will read from this stream of types/properties from the schema
• Let users build/update/browse the schema against the Knowledge Graph (like the TypeSync app currently allows in the "Define Schema" step of the create app functionality)
• Let users overwrite their existing schema.ts and mapping.ts files with the changes they make in the TypeSync app