Settle on a baseline kubernetes env which target deployments can be rolled out to

In my opinion there is a clear separation between getting baseline k8s cluster functionality involving networking and storage functionality with the host machine and then the user elected matrix of applications which are configured on top of this baseline.

This somewhat parallels the relationship between obolup and obol-cli, where obol-up should aim to stand up this baseline "empty" cluster. obol-cli or some other methodology would apply the application matrix with a healthy baseline in operation.

Currently obol-up is doing both and obol-cli isn't doing anything at all. Considering the two repos as is, the two tools could be merged where obol-up is just a sub-cmd in obol-cli. Also new features like obol down/clean are possible