bedrock `setup` doesn't auto-populate config values from existing config file

[andrebriggs]

Repro:

1. Use bedrock init -i to setup an config file at ~/.bedrock/config.yaml
2. Call bedrock init -i and see that the first prompt already has a value filled in for you

$ bedrock init -i
? Enter organization name
 (myOrg) 

3. Then call bedrock setup and the first prompt doesn't already have a value filled in for you

$ bedrock setup
info:    az cli vesion 2.5.1
? Enter organization name

I would expect the following

$ bedrock setup
info:    az cli vesion 2.5.1
? Enter organization name
(myOrg) 

[dennisseah]

when we design setup command, we hope to provide a way to jumpstart user from ground zero to a functional setup. And the thinking is that there are no spk config file to start with.

[andrebriggs]

Dennis Seah (@dennisseah) makes complete sense. If we are coming from the POV that they will never call bedrock init then we can ignore this