Update modis session auth

[ShengpeiWang]

Description

• Added support to try HTTPProxyAuth for the first data download of a session.
• No change to the public interface, and fully backward compatible
• The issue was getting No file location found, when we tried to download MOD13A2 tiles this week. When we checked the download link on the browser, the authentication request was directed to urs.earthdata.nasa.gov and can no longer be accomplished with HTTPBasicAuth.
• Considerations I'd like reviewer input on: In order to use a different authentication, the user info need to be passed through the methods in the GranuleHandler class. I chose to pass the modis_session object along, but I'm still thinking about whether there is a cleaner way to do it.
  1. one issue is that the session object is a part of the modis_session object, so there's currently redundant information being passed into the methods. I'm not sure if we wang to make large scale refactoring change here.
  2. which class ( GranuleHandler vs ModisSession) should worry about the implementation detail of using HTTPProxyAuth. I have tried both ways, and the current version is cleaner in code and logic.

Type of change

Please delete options that are not relevant.

• [x] 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

How Has This Been Tested?

• [x] RP can download granules successfully now
• [x] all existing unit tests still pass

Checklist:

• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules
• [x] I have checked my code and corrected any misspellings

Next Steps

• [ ] Assign a reviewer based on the code owner document.

• [ ] Once your review is approved, merge and delete the feature branch

On behalf of the Modis Tools Dev Team, thank you for your hard work! ✨

[ShengpeiWang]

@jamie-sgro in your comment, the code got copied again to the stack trace section, do you mind showing me the trace again? I also tried your code locally, and it worked fine.

[jamie-sgro]

@ShengpeiWang I got a max retries failure but I've tested it now and it seems to be working fine. My thought is that it was just bad timing against the live API. Gotta love being dependent on live external services like that. I'll review your code proper now that I can greenlight

[ShengpeiWang]

@jamie-sgro, thanks for the explanation and resource pointers! I made the changes to pass around only modis_session in 9117876. Can confirm that the code still runs as expected.

Regarding the other point, yeah I did not want to over engineer things. Given requests is a standard library, I think it's OK to not obscure interactions with it.