[ENH] - Validate instance types for Google Cloud

[marcelovilla]

Feature description

Right now, we're not validating whether instance types passed in the configuration are valid when initializing the infrastructure. However, we're doing it for AWS and DigitalOcean. See:

• nebari/src/_nebari/stages/infrastructure/__init__.py

  Line 517 in aed2b92

  available_instances = amazon_web_services.instances(data["region"])

• nebari/src/_nebari/stages/infrastructure/__init__.py

  Line 282 in aed2b92

  available_instances = {_["slug"] for _ in digital_ocean.instances()}

Value and/or benefit

Besides being consistent with what we have with other providers, it would enhance the user's experience when specifying unavailable/non-existing instance types before running into an error halfway through the deployment.

Anything else?

No response

[marcelovilla]

@blakerosenthal since you're interested in this issue, here are a couple pointers that you might find useful:

• We'll likely need to implement the instances function in the following file: https://github.com/nebari-dev/nebari/blob/379736eb365ca5f7c5da769d578df5961bb644c2/src/_nebari/provider/cloud/google_cloud.py
• We recently merged a PR (see: Use Google Auth and Cloud Python APIs instead of gcloud CLI #2083). In that PR we switched from using subprocess + gcloud to using the Google Python APIs. We used to have an instances function but it was not being used anywhere so we got rid of it and opened this issue to make sure we'd implement it using the Google Python APIs in the future.