Prevent OpenLineage failure when BigQuery table metadata is missing

[KamranImaaz]

Fixes #60096

What

Adds a safety condition to OpenLineage extraction to prevent errors when
BigQueryUpdateTableSchemaOperator, BigQueryUpdateTableOperator, or
BigQueryUpsertTableOperator do not return a table resource.
Also removes duplicate and unused imports and updates type annotations
to use dict | None where applicable.

Why

OpenLineage callbacks run after task execution and should not cause
task failures when metadata is unavailable.

[KamranImaaz]

Hi @potiuk, I’ve addressed #60096 with a safety guard for OpenLineage and cleaned up the PR.
Would appreciate your review when convenient. Thanks!

[jroachgolf84]

@KamranImaaz, do you think it might make sense to add a unit test or two to validate this new logic?

[KamranImaaz]

@KamranImaaz, do you think it might make sense to add a unit test or two to validate this new logic?

Yes @jroachgolf84 currently working on it. Thanks for pointing it out.

[KamranImaaz]

@jroachgolf84 I have added unit test to cover the case when _table is None. Requesting you to check it.

[kaxil]

PR title doesn't confirm to standards -- it doesn't say anything much.

[KamranImaaz]

PR title doesn't confirm to standards -- it doesn't say anything much.

@kaxil I have updated the title. pls check it.

[potiuk]

You need to rebase it and fix the errors

[KamranImaaz]

You need to rebase it and fix the errors

Sure @potiuk

[KamranImaaz]

You need to rebase it and fix the errors

Hi @potiuk I have gone through the CI Checks error specifically build documentation(docs only). So far what I have understood is that type annotations for execute method(ex: def execute()-> dict | None) is causing error. I'm i correct?

[potiuk]

You definitely have checks that can be fixed by installing prek and running it as suggested in both - the error and contributor's guide, and you have some doc error that you can try to build locally (again following our contributing guidelines describing how to build doscs)l

Also you have to rebase and resolve the conflicts you have - so rebasing (also described in the contribution guide) is something you should start with.

[KamranImaaz]

You definitely have checks that can be fixed by installing prek and running it as suggested in both - the error and contributor's guide, and you have some doc error that you can try to build locally (again following our contributing guidelines describing how to build doscs)l

Also you have to rebase and resolve the conflicts you have - so rebasing (also described in the contribution guide) is something you should start with.

Yes I have rebased it and resolved the conflicts. Need to check the errors locally. Thanks!