Since yup_oauth2 structs are used as parameters in public functions there is already semver coupling, as it is an error if consumer uses different version of yup_oauth than gcp-bigquery-client
Export yup_oauth2 so consumers don't need to carefully keep their dependency versions in sync. This also allows accessing yup_oauth2::hyper_rustls, as suggested in #85
Since yup_oauth2 structs are used as parameters in public functions there is already semver coupling, as it is an error if consumer uses different version of yup_oauth than gcp-bigquery-client
Export yup_oauth2 so consumers don't need to carefully keep their dependency versions in sync. This also allows accessing yup_oauth2::hyper_rustls, as suggested in #85