### Apache Airflow version

Other Airflow 2 version (please specify below)

### What happened

Using Apache Airflow 2.4.3 and apache airflow google provider 8.4 (also tried with 10.1.0).
We have a query that in production should run for a long time, so we wanted to make the BigQueryInsertJobOperator deferrable.
Making the operator deferrable runs the job, but the UI and triggerer process don't seem to be notified that the operator has finished.
I have validated that the query is actually run as the data appears in the table, but the operator gets stuck in a deferred state.

### What you think should happen instead

After the big query job is finished, the operator should exit it's deferred state.

### How to reproduce

Skeleton of the code used

```
with DAG(
    dag_id="some_dag_id",
    schedule="@daily",  
    catchup=False,
    start_date=pendulum.datetime(2023, 5, 8),
):
    extract_data = BigQueryInsertJobOperator(
        task_id="extract_data",
        impersonation_chain=GCP_ASTRO_TEAM_SA.get()
        params={"dst_table": _DST_TABLE, "lookback_days": _LOOKBACK_DAYS},
        configuration={
            "query": {
                "query": "{% include 'sql/sql_file.sql' %}",
                "useLegacySql": False,
            }
        },
        outlets=DATASET,
        execution_timeout=timedelta(hours=2, minutes=30),
        deferrable=True,
    )
```

### Operating System

Mac OS Ventura 13.3.1

### Versions of Apache Airflow Providers

apache airflow google provider 8.4 (also tried with 10.1.0).

### Deployment

Official Apache Airflow Helm Chart

### Deployment details

We're using astro and on local the Airflow environment is started using `astro dev start`. The issue appears when running the DAG locally.
An entire other issue (may be unrelated) appears on Sandbox deployment.

### Anything else

Every time the operator is marked as deferrable.
I noticed this a few days ago (week started with Monday May 22nd 2023). 

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)

"""Change some fields of a table.
        Use ``fields`` to specify which fields to update. At least one field
        must be provided. If a field is listed in ``fields`` and is ``None``
        in ``table``, the field value will be deleted.
        If ``table.etag`` is not ``None``, the update will only succeed if
        the table on the server has the same ETag. Thus reading a table with
        ``get_table``, changing its fields, and then passing it to
        ``update_table`` will ensure that the changes will only be saved if
        no modifications to the table occurred since the read.
        :param project_id: The project to create the table into.
        :param dataset_id: The dataset to create the table into.
        :param table_id: The Name of the table to be created.
        :param table_resource: Table resource as described in documentation:
            https://cloud.google.com/bigquery/docs/reference/rest/v2/tables#Table
            The table has to contain ``tableReference`` or ``project_id``, ``dataset_id`` and ``table_id``
            have to be provided.
        :param fields: The fields of ``table`` to change, spelled as the Table
            properties (e.g. "friendly_name").
        """
        fields = fields or list(table_resource.keys())
        table_resource = self._resolve_table_reference(
            table_resource=table_resource, project_id=project_id, dataset_id=dataset_id, table_id=table_id
        )
        table = Table.from_api_repr(table_resource)
        self.log.info("Updating table: %s", table_resource["tableReference"])
        table_object = self.get_client(project_id=project_id).update_table(table=table, fields=fields)
        self.log.info("Table %s.%s.%s updated successfully", project_id, dataset_id, table_id)
        return table_object.to_api_repr()
    @GoogleBaseHook.fallback_to_default_project_id
    def patch_table(