Chores needed for a clear code base structure

[unkcpz]

We did release the 2.1.0 I guess we can do some cleaning on the package management to make code base structure a bit more clear? Here are things I think we can do, let me know if you think there are any risk that will bring the risk of break apps.

• Remove aiidalab-widgets-base from registry #550
• Publish AWB on conda-forge #595
• Using pyproject.toml, this will happened only after the package is out from app registry.
• Move modules to folder (but should make sure the old module import still work for backward compatibility).
• Rename the default branch master -> main

@yakutovicha @danielhollas do you agree or have more things that we can do?

[danielhollas]

I think this is blocked on first integrating AWB into the Docker image. Which in turn means that we need to publish AWB to conda-forge. I am happy to do that since I wanted to learn how to do it.
But first I would also like to tackle #392 so that we do not blow up image size.

[unkcpz]

that we do not blow up image size.

I was more worried if we find the speed of starting a container can be improved by having a $HOME prepared, do we do it if it increase the image size? How much we really need to worried about the image size since after the user start using the image, may not avoid to have most of dependencies are installed.