Support location for BigQueryInsertJobOperator in deferrable mode

[moiseenkov]

This PR provides a workaround solution for the issue #35833.

It is really necessary because users are unable to use BigQueryInsertJobOperator in deferrable mode in regions other than EU, US or us-central1. This fix was provided now because there is no response neither from gcloud-aio nor google-cloud-bigquery regarding their plans for providing async get_job method with the optional location parameter.

The proposed solution:

1. The BigQueryAsyncHook wraps the call of the synchronous method BigQueryAsyncHook.get_job() in asyncio.loop.run_in_executor().
2. The optional parameter location is passed from the BigQueryInsertJobOperator to the BigQueryInsertJobTrigger, where it is handed to the hook.
3. Because the BigQueryInsertJobTrigger is a parent class for other four triggers (see below), they were updated in order to comply with the base class attributes.

BigQueryCheckTrigger,
BigQueryGetDataTrigger,
BigQueryIntervalCheckTrigger,
BigQueryValueCheckTrigger

4. Despite the modification, triggers from (3) and all the operators that use these triggers and changed async method BigQueryAsyncHook.get_job_status() don;t change behavior because the optional parameter location is ignored there. However, it would be very nice to fix them too and test carefully in a separated PR:

BigQueryCheckOperator,
BigQueryGetDataOperator,
BigQueryIntervalCheckOperator,
BigQueryValueCheckOperator,
BigQueryTablePartitionExistenceSensor,
BigQueryToGCSOperator,
GCSToBigQueryOperator

closes: #35833

[VladaZakharova]

Hi @eladkal @potiuk !
Can you please check changes in this PR? Thank you!

[spencertollefson]

A little late here - but gcloud-aio released today the inclusion of a location parameter:
https://github.com/talkiq/gcloud-aio/releases/tag/bigquery-7.1.0

Perhaps with this work around merged in, we no longer need it. But we could also build around leveraging that param now.