remove defaultScope from customScope

[ptunay]

Issue: #25

For cases when we don't need the 'https://www.googleapis.com/auth/drive.readonly' scope and supply our own customScope

[mkosik]

This is very important for prod, since the current default scope is "restricted" & requires a very difficult verification process.
See: Google OAuth API verification FAQs
Without this change, it makes this library as is practically unusable in prod for many.

Even Google recommends just "https://www.googleapis.com/auth/drive.file" scope, which is specifically not restricted.
See: Drive Picker API Docs

[mkosik]

Would also recommend to update defaultScopes to "https://www.googleapis.com/auth/drive.file", as well as customScopes mentioned in demo/src/App.tsx and /README.md as recommended by aforementioned Drive Picker API Docs, so the new users of the lib won't be confused.

[filippofilip95]

During the verification process from Google they recommended us to use https://www.googleapis.com/auth/drive.file only, instead of the defaultScope which is used in the lib.

We'd appreciate the merging of this PR as well.

[Ayan-Bandyopadhyay]

Also ran into this issue because I needed to use the drive.file scope in my app, so merging in this PR would be nice. In the meantime I've made a fork with the fix for anyone that needs it: https://github.com/psychic-api/React-google-drive-picker

[fyelci]

I forked this repo and published as @fyelci/react-google-drive-picker. This should solve the issue. I also upgraded dependencies.

https://www.npmjs.com/package/@fyelci/react-google-drive-picker

[ianpandis]

During the verification process from Google they recommended us to use https://www.googleapis.com/auth/drive.file only, instead of the defaultScope which is used in the lib.

We'd appreciate the merging of this PR as well.

Having this same issue.