builds: make pre-requisites explicit

[antoniivanov]

First time building of the project locally start from running
./cicd/build.sh . It's good idea to also check for any pre-requisites
required in order to buld all components.

I think that the top level build should not try to build different
projects. Each project should be independant of all other projects (as
if they were in different git repo). This would enfore keeping them
decoupled from each other (no build time dependencies) and facilitate
easer parallel development (people devloping on vdk-core would not
impact those making changes in control-service.

Testing Done: In empty env (using docker):
docker docker run -it -v "$(pwd):/vdk" ubuntu /bin/bash
./cicd/build.sh - prompted to install python and warn me for missing
java
After installing conda - was able to run ./cicd/build.sh succesfully
Then ran vdk-core and vdk-control-cli build succesfully.

control-service build is failing currently and this will be fixed
separately.

[ivakoleva]

So root/cicd/build.sh is used to mainly check prerequisites, and print what you need to do next in plaintext;
I am okay with that - I would also be okay if root is able to build everything at once - just to have this enabled if someone wants to rebuild all the components altogether.

About the main build.sh output, again it seems useful for each component contextual ./cicd/build.sh, to be runnable from anywhere - without user changing directories explicitly. It's more convenient, and fail-prone.

I also did build each component successfully, using the build scripts.