Staging sparc api

[Tehsurfer]

Description

This branch is used with https://scicrunch.org/api/1/elastic/SPARC_PortalDatasets_stage

It pulls files from the pennsieve python api as opposed to the discover s3 bucket.

When using this branch, calls on the front end using the s3-resource/<path:path> will be grabbed from the pennsieve python client.

Note that in order for this to work the PENNSIEVE_API_SECRET and PENNSIEVE_API_TOKEN keys must have access to the dataset of interest. This should not be an issue if the keys are a member of the SPARC Data Curation Team on pennsieve.

Type of change

Delete those that don't apply.

• 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)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added unit tests that prove my fix is effective or that my feature works