[FEATURE] Package structure changes for project

[shravanshetty1]

Any suggestions regarding package structure changes should be made here and should be handled in a seperate issue

@Sriep
We can come to consensus about package structure changes here -

Suggestion: GitHub expects Go repositories to have their root directory be a Go source directory. I recommend collapsing the code/go/0chain.net directories. So that the contents of 0chain.net is added to the blobber root, and the code directory deleted. This way the Blobber's go package structure will not change, it will just be more readily available to GitHub actions.

I agree with the above suggestions.

Would like to add that we should move all 'main' packages in cmd directory. We should also review and remove unneeded packages such as docker.aws probably rename docker.local to something else, the conductor is probably not used anymore, bin directory can be merged with docker.local.

[guruhubb]

We can take out docker.aws but keep everything as is since we use them and can take up package restructure after mainnet or as the last item

[kushthedude]

A suggestion over the directories here,
Most of the docker.*** directories contains helper scripts to setup the 0chain components on bare metal or any of the cloud provider. More over all of our core-packaged are placed under code/go/***
A modern yet understandable structure over here would be

installation/{all-helper-utils}
cmd/{entry points}
handlers/{api-endpoints}
pkg/{all-core-packages/util-packages}
db/migrate{sql-scripts here}
config
docs

The following repository structure is what we used in general at Msft & is also used by many oss projects. The current structure is not much well oriented as https folder contains install script for https server over ec2 & other mismatch.

Wdyt @guruhubb ? I can do this changes and push it to any other branch.