fix gdrive endpoint for tests

[AlexVCaron]

Quick description

Tests are not passing because of a confirmation on large file download from gdrive. This fies the endpoint used so the confimation works.
...

Type of change

Check the relevant options.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Provide data, screenshots, command line to test (if relevant)

Run the tests or wait for Jenkins

Checklist

• My code follows the style guidelines of this project (run autopep8)
• I added relevant citations to scripts, modules and functions docstrings and descriptions
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I moved all functions from the script file (except the argparser and main) to scilpy modules
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[arnaudbore]

Build passed ! Good Job 🍻 !

[arnaudbore]

Build passed ! Good Job 🍻 !

[AntoineTheb]

Could it be a good time to move away from Google Drive for test data ? Something like git-lfs ? They could be in a separate repo, which would be pulled when running tests. We could even pull specific branches which include new test data whenever we need to add more !

[AlexVCaron]

Yes., this is a temporary fix. We are testing DVC right now, it looks like it'll do the trick.