quota_project_id not exposed at operator level for Google Cloud operators

[Ankurdeewan]

Description

Just noticed this while working on #56324 — quota_project_id was added to GoogleBaseHook but none of the Google Cloud operators expose it as a parameter. The only way to use it right now is through connection extras, which is connection-wide and can't be overridden per task. Every operator already does this pattern for impersonation_chain,quota_project_id just needs the same treatment.
I'm planning to implement this; starting with BigQuery operators and then GCS, Dataflow, and Dataproc.
Happy to submit a PR for this! just wanted to check if there's any reason this pattern shouldn't be extended to operators before I start.

Use case/motivation

if you have two BigQuery tasks in the same DAG that need to bill to different projects, there's currently no way to express that at the operator level. Organizations using shared service accounts across multiple billing projects hit this immediately.

Related issues

#56324

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[jroachgolf84]

@Ankurdeewan - how frequently do you think that a user would use the quota_project_id? I think it might make more sense to leverage extras for something like this?

[Ankurdeewan]

That's a fair point. The main case I had in mind was when you have two tasks in the same DAG billing to different projects -extras won't help there since it's connection-wide. But yeah, if that's considered too niche I'm totally open to dropping it.

[jroachgolf84]

Could two Connections be a possibility?