fix: Dataproc operators fail to import without OpenLineage

[kacpermuda]

related: #46478

This PR does three things:

1. Moves top level import from Google's OpenLineage utils into operator's execute method, to avoid issues with ImportError, should they happen in the future.
2. Adds try/except for OpenLineage code in DataProc operators, so that any error related to OpenLineage does not affect execution of DataProc.
3. Moves BigQueryJobRunFacet to a separate file and add try/except on class definition, in case OpenLineage is not available (similar logic as in common.compat provider). I've also moved the import of this facet into specific method in _OpenLineageMixin, so it's no longer top level import.

I've tested it manually on the environment without OpenLineage and the error described in the issue is gone after applying changes included in this PR.

CC @mobuchowski

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[potiuk]

Nice. Some mypy checks but it looks good :)

[potiuk]

Quick fix @kacpermuda :)

[kacpermuda]

@potiuk let's hold on with merging until we get @mobuchowski approval. We discussed few ways to solve this, and I want to hear his opinion.

[potiuk]

Sure

[mobuchowski]

No need to be a single point of failure 🙂
PR looks good to me.