Create a pipeline to ingest the PWD parcels into a bigquery table

[mjumbewu]

Refer to issue #5 for details

Acceptance Criteria:

• [ ] A Cloud Function named extract-pwd-parcels to fetch the PWD Parcels dataset and upload into a Cloud Storage bucket named musa509s23_team<N>_raw_data into a folder named pwd_parcels/
• [ ] A Cloud Function named prepare-pwd-parcels to prepare the file in gs://musa509s23_team<N>_raw_data/pwd_parcels/ for backing an external table. The new file should be stored in JSON-L format in a bucket named musa509s23_team<N>_prepared_data and a file named pwd_parcels/data.jsonl. All field names should be lowercased.
• [ ] A Cloud Function named load-pwd-parcels that creates or updates an external table named source.pwd_parcels with the fields in gs://musa509s23_team<N>_prepared_data/pwd_parcels/data.jsonl, and creates or updates an internal table named core.pwd_parcels that contains all the fields from source.pwd_parcels in addition to a new field named property_id set equal to the value of parcel_number.
• [ ] A parallel branch added to the Workflow named data-pipeline to run each function in step.

[nlebovits]

PRs #21 and #23 address items 1, 2, and 3. Will tackle 4 (parallel branch) today in class.

[nlebovits]

closed by #30, #32