Add table gcp_storage_object. Closes #459

[karanpopat]

Integration test logs

Logs

Add passing integration test logs here

Example query results

Results

select
  bucket,
  count(*) as total_objects,
  sum(size) as total_size_bytes
from
  gcp_storage_bucket_object
group by
  bucket;

+-----------------------------------------------------------+---------------+------------------+
| bucket                                                    | total_objects | total_size_bytes |
+-----------------------------------------------------------+---------------+------------------+
| dataproc-81d7c6b8-6d8c-4b04-af65-1bf0751bd6fd-us-east1    | 24            | 6977205          |
| dataproc-e8a44e2b-a18a-403f-a10f-75f15145c765-us-central1 | 6             | 25191            |
| dataproc-staging-asia-southeast2-979620418102-a1jautgv    | 1             | 4213             |
| gcf-sources-979620418102-us-central1                      | 12            | 1508778          |
| kp-bucket-22-7-23                                         | 1             | 38961            |
| kp-test1-22-7-23                                          | 1             | 38961            |
+-----------------------------------------------------------+---------------+------------------+

Time: 4.2s. Rows fetched: 45. Hydrate calls: 0.

[cbruno10]

@karanpopat Please see review comments, thanks!

[cbruno10]

I wouldn't use a parent hydrate for this table, as there could be a lot of buckets with a lot of objects, so if someone runs select * from gcp_storage_object, they could be waiting a long time (we made the same decision with aws_s3_object.

[cbruno10]

Suggested change

	Name: "gcp_storage_bucket_object",
	Name: "gcp_storage_object",

Even though TF calls it gcp_storage_bucket_object, I think we should deviate here, unless this new name is ambiguous and there are other GCP Storage objects

[cbruno10]

@karanpopat Thanks for making the previous changes, left 1 more, please have a look, thanks!