Is your feature request related to a problem? Please describe.
The current configuration of the bigquery.LoadJobConfig() in the bigquery offline store leaves the create_disposition undefined, defaulting to "CREATE_IF_NEEDED", which requires the service account that is sending the data from the feast server into the offline store to be given the bigquery.tables.create. This is not ideal for our setup, as our tables will be created and managed by a different service separate to feast, and giving the SA this permission would create a risk of data exposure.

Describe the solution you'd like
A way to allow users to declare the type of create_disposition they'd want, defaulting to the existing behaviour if left unset.

Describe alternatives you've considered
Maintain a fork of feast with this modification made.