Code reorganization

[andre-senna]

EPIC

• Move das-attention-broker repo content into das repo #161 <-- done
• Move das-atom-db repo content into das repo #164 <-- in progress
• [C++ repos] Add test coverage check #118
• Check how to build and publish hyperon-das-atomdb-cpp for multiple targets/platforms #141
• Cleanup external lib usage #142

[angeloprobst]

My suggestion is to unify all related repos (das-attention-broker, das-query-engine, das-atomdb and das-node) into das repository, and then deprecate or delete the original repositories once everything is working and building and being deployed from the das repo.

By doing that, das repo would have a new src directory, to where the code from the other repos would be moved in.

An example of how this new src subdir tree would look like (considering that nanobind projects require CMake-style building but the rest will be managed by Bazel):

src/
├── cpp/
│   ├── atom_db/
│   │   └── BUILD
│   ├── attention_broker/    <-- formerly `attention_broker_server`
│   │   └── BUILD
│   ├── common/
│   │   └── BUILD
│   ├── das_node/
│   │   └── BUILD
│   ├── query_engine/
│   │   └── BUILD
│   └── BUILD
├── nanobind/
│   ├── common/
│   ├── hyperon_das_atomdb_cpp/
│   │   ├── CMakeLists.txt
│   │   └── pyproject.toml
│   └── hyperon_das_node/
│       ├── CMakeLists.txt
│       └── pyproject.toml
├── python/
│   ├── common/
│   │   └── BUILD
│   ├── hyperon_das/
│   │   └── BUILD
│   ├── hyperon_das_atomdb/
│   │   └── BUILD
│   └── BUILD
├── BUILD
└── WORKSPACE

[andre-senna]

Makes total sense.

BTW you can drop the "server" from the name of the Attention Broker module.