Simplify/consolidate project structure

[DamianReeves]

Feature Request

Simplify the project structure:

Description of Problem:

Today we have quite a few modules/projects, which is an artifact of how development has been done (trying some ideas, and wanting to not mix that with core Morphir, as well as previously having a Scala 3 compiler plugin as a goal while wanting to still Support Scala 2).

Today, it feels like there are a bit too many projects (at least for the core of what we are doing).

Potential Solutions:

Going to aim for something along the lines of the following:

.
└── morphir
    ├── build
    │   └── integration
    │       ├── mill
    │       └── sbt
    ├── interop
    │   ├── tapir
    │   ├── vulcan
    │   └── zio
    │       ├── json
    │       └── schema
    ├── knowledge
    ├── macros
    ├── main
    ├── testing
    └── web
        ├── client
        └── server

Let's discuss what we have here:

Here's as summary of the thinking here:

Project	Description
morphir	This project contains what you need to work with the Morphir data formats: IR & MDM (Morphir data model). It will also contain the implementation of the SDK and the runtime.
morphir/build/integration	Projects contained in this folder house various build integrations morphir-scala intends on providing
morphir/interop	Projects contained in this folder, are meant to house the different interop libraries we will provide with other libraries (i.e.): zio-json (for JSON), zio-schema, tapir (for API/OpenAPI), vulcan (for Avro), and others
knowledge	An implementation of logic programming meant to eventually interop better with Morphir.
macros	Macros needed to support the main morphir module.
main	The main CLI that allows users to interact with Morphir.
testing	Testing helpers used internally by the project
web/client	Client-side code for the morphir develop/morphir live tooling you can run in the browser.