Restructure repository around 'optimake' package

[ml-evs]

This PR refactors the repository to focus on the newly named optimake Python package. For now I've retained optimade_launch as another package in the src directory, but have left it unlisted in the pyproject.toml. None of the code usage should change except changing imports from mc_optimade to optimake.

[eimrek]

awesome, thanks, i'll take a detailed look later today. However, just to quickly mention, the only thing that i'm currently using from optimade-launch is the data injection to mongoDB (https://github.com/materialscloud-org/optimade-maker/blob/main/src/optimade_launch/optimade_launch/database.py). I am wondering if this is maybe of more general interest and should also be moved to optimake? Or would it be better to move this to the MC-implementation-specific repository?

[ml-evs]

awesome, thanks, i'll take a detailed look later today. However, just to quickly mention, the only thing that i'm currently using from optimade-launch is the data injection to mongoDB (https://github.com/materialscloud-org/optimade-maker/blob/main/src/optimade_launch/optimade_launch/database.py). I am wondering if this is maybe of more general interest and should also be moved to optimake? Or would it be better to move this to the MC-implementation-specific repository?

Yeah, I was thinking of moving this too. Then we can have optimake serve and optimake validate (#45) based on it + mongomock. Perhaps we could merge this first and then I'll follow-up with a new PR + tests?

[eimrek]

Looks good!