chore: Create ml_datasets_uscentral1 for penguins table

[adlersantos]

Description

Note: This PR is based out of a feature branch (#203) that now supports adding alternative BQ datasets.

BQ datasets are location-specific, but we (internally) need an ml_datasets_uscentral1 for upcoming ML guides and tutorials. This PR adds that dataset, which loads the same penguins table under it.

Checklist

• Please merge this PR for me once it is approved.
• If this PR adds or edits a dataset or pipeline, it was reviewed and approved by the Google Cloud Public Datasets team beforehand.
• If this PR adds or edits a dataset or pipeline, I put all my code inside datasets/<YOUR-DATASET> and nothing outside of that directory.
• This PR is appropriately labeled.

[adlersantos]

cc @ivanmkc

[leahecole]

LGTM but @tswast should probably be final reviewer since he has additional context

[tswast]

LGTM

Technically the GCS-to-GCS step is not needed because the samples data bucket already has a copy in gs://cloud-samples-data-us-central1, but since we want this to also be useful as a potential example for future data sources where that is not the case I think it makes sense to keep it.

[adlersantos]

@tswast Thanks a lot!

I had to add the intermediate GCS-to-GCS step because I started getting this error on the DAG when loading to ml_datasets_uscentral1:

google.api_core.exceptions.BadRequest: 400 
Cannot read and write in different locations: source: US, destination: us-central1

But yes, this can be a reference pattern that others who are encountering the same issue can refer to.