Feature Request Serialization of Google Client ID and Client Secret

The current implementation for the Google Sheets Service through the SheetsServiceProvider scriptable object allows the developer to load their credentials from a json file downloaded from google. But those credentials are then serialized as part of the asset, and show up in source control diffs.

We'd like to avoid those going into source control. While we can tell developers not to commit those changes, it's prone to happen accidentally.

It would be ideal if we could instead point the SheetsServiceProvider at the json file itself, and it then loaded the credentials when needed, but didn't store them as part of the asset. The json file could then be kept outside the repo, and distributed to developers as needed, keeping the credentials out of source control.