feat: Adding billing_project_id in BigQueryOfflineStoreConfig

[vmallya-123]

Signed-off-by: “Varun varun.mallya@tech.jago.com

What this PR does / why we need it:
One is able to add big query billing project, this can enable to run Bigquery job in a separate project which is not the project which has the BQ feature datasets. Useful in cases when certain projects have reservations (slots) for Bigquery jobs to run.

[adchia]

/ok-to-test

[adchia]

were you able to verify this works? also what does the regular project_id do when billing_project_id is set?

[codecov-commenter]

Codecov Report

Base: 67.46% // Head: 76.69% // Increases project coverage by +9.23% 🎉

Coverage data is based on head (9bdbab9) compared to base (0ad7fe3).
Patch coverage: 77.27% of modified lines in pull request are covered.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3253      +/-   ##
==========================================
+ Coverage   67.46%   76.69%   +9.23%     
==========================================
  Files         179      216      +37     
  Lines       16400    18260    +1860     
==========================================
+ Hits        11064    14005    +2941     
+ Misses       5336     4255    -1081     

Flag	Coverage Δ
integrationtests	67.32% <76.19%> (-0.14%)	⬇️
unittests	58.15% <22.72%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
sdk/python/feast/infra/offline_stores/bigquery.py	85.57% <77.27%> (-0.78%)	⬇️
sdk/python/feast/infra/registry/base_registry.py	92.85% <0.00%> (-0.70%)	⬇️
...on/feast/infra/materialization/snowflake_engine.py	93.18% <0.00%> (-0.41%)	⬇️
...tion/contrib/spark/spark_materialization_engine.py	71.84% <0.00%> (-0.28%)	⬇️
...ests/integration/e2e/test_python_feature_server.py	100.00% <0.00%> (ø)
.../online_stores/contrib/hbase_online_store/hbase.py	37.25% <0.00%> (ø)
...tion/feature_repos/universal/online_store/mysql.py	53.84% <0.00%> (ø)
...tion/feature_repos/universal/online_store/hbase.py	50.00% <0.00%> (ø)
...ib/trino_offline_store/test_config/manual_tests.py	33.33% <0.00%> (ø)
..._stores/contrib/postgres_offline_store/postgres.py	34.14% <0.00%> (ø)
... and 106 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[vmallya-123]

@adchia yes I tried it and it works as expected. The project_id is the GCP project which has the feature view datasets, this will be the project_id which will be used by the query template etc (as it is currently being used). billing_project id is the GCP project where the big query job would actually run.

[adchia]

/lgtm

[adchia]

mind fixing the lint errors and the title to conform to semantic release convention?

[vmallya-123]

Thanks for fixing the lint error
Is the title better now? Following the instructions given here

Ensure the title of the PR matches semantic release conventions (e.g. start with feat: or fix: or ci: or chore: or docs:). Keep in mind that any PR with feat: or fix: will directly make it into the change log of a release, so make sure they are understandable!
Please let me know if there is anything else I can do

[adchia]

/lgtm

[feast-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adchia, vmallya-123

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [adchia]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment