HyP3 SDK user approval check has unintended consequences

[jtherrmann]

Jira: https://asfdaac.atlassian.net/browse/TOOL-2909

Note: The above link is accessible only to members of ASF.

---

HyP3 SDK v6.2.0 introduced a query to the /user endpoint when creating a new HyP3 object, so that unapproved users receive a warning message. Unfortunately, this has had some unintended consequences, including:

• ServerError from HyP3 constructor for users with many past jobs #280
  • Blocks Bump hyp3-sdk from 6.1.0 to 7.0.0 its-live-monitoring#115
• Failing tests for Bump hyp3-sdk from 6.1.0 to 7.0.0 hyp3-event-monitoring#76
  • See https://github.com/ASFHyP3/hyp3-event-monitoring/actions/runs/9749311948/job/26906187813?pr=76

This feature was probably of limited value to begin with, and is currently serving no purpose because we haven't enabled user whitelisting in HyP3. We should consider adding an option to bypass this check when creating a HyP3 object, or revert the new feature altogether if we don't foresee it ever adding much value.