[ENH] - Allow setting region during init

[pmeier]

Feature description

We currently hard-code the following regions based on the cloud provider the user selects:

nebari/nebari/initialize.py

Lines 217 to 218 in 1413b95

	DIGITAL_OCEAN = {
	"region": "nyc3",

nebari/nebari/initialize.py

Lines 228 to 230 in 1413b95

	GOOGLE_PLATFORM = {
	"project": "PLACEHOLDER",
	"region": "us-central1",

nebari/nebari/initialize.py

Lines 239 to 240 in 1413b95

	AZURE = {
	"region": "Central US",

nebari/nebari/initialize.py

Lines 260 to 261 in 1413b95

	AMAZON_WEB_SERVICES = {
	"region": "us-west-2",

However, similar to the deploy target, the region has no good default value. Worse, nebari init doesn't even give you the option to set the region and one has to manually edit the yaml afterwards.

1. We should expose a --region option on nebari init
2. The option should be required in case a new cloud provider, i.e. not "local" or "existing" is used as deploy target.

For the guided init, we should add a question for the region (preferably a populated list) that will be displayed if the user selects one of the cloud providers.

Value and/or benefit

Less frustration due to failed deploys and time needed manually editing the config yaml.

Anything else?

No response

[pavithraes]

@iameskild - Can be added to the "Advanced Configuration" section of guided init

[pmeier]

I don't think it falls under "advanced". We don't want a default value in case the user specifies a cloud provider. However, since most people will not open the advanced settings, we'll need to have a default if we put it there.