223 - Integrate Github API to the request data form for filing issues in refinebio repo

[nozomione]

Issue Number

Closing #223

Purpose/Implementation Notes

• Temporarily using a test repo for local development, but the correct values (endpoint and token) for staging and production have been added to Vercel.

---

Integrated the Github API to the request data form for creating an issue in refinebio repo:

• Request Search Data Form via Search (terms with no search results)
• Request Experiment Data Form via the "Request Experiment" button (experiments with non-downloadable samples)

Via Request Search Data Form When a user makes a data request, the application redirects to the homepage and displays a notification banner based on the request status (Error = GitHub and/or HubSpot failed, Success = both successful).

Success banner:

Error banner (also the failed data request will be posted in Slack CCDL channel):

Via Request Experiment Data Form If the data request was successful, the application marks the experiment as requested in the search card, otherwise the failed data request will be posted in Slack CCDL channel:

Types of changes

• New feature (non-breaking change which adds functionality)

Checklist

• [x] Lint and unit tests pass locally with my changes
• [x] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added necessary documentation (if appropriate)
• [ ] Any dependent changes have been merged and published in downstream modules

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
refinebio-web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 13, 2024 4:54pm

[nozomione]

@davidsmejia I've made some adjustments to this PR based on the latest updates in #300.

I've also resolved the parsing error. Please review the following commit:

• 5cc8eed5439b739c61aae6eaeb29af27330a62df
• fbf0dcd72b8cf01c8f32573993ddad0232ec3722

Thank you David!

[nozomione]

@davidsmejia based on 1:1 feedback, I've adjusted the codebase (pls see commit at 79daaf0b2d8ccf72b670a5485d21f7fafaf5b670), thank you David!

(NOTE: I added the return statement to the end of api/data-requests just to prevent the eslint[consistent-return](https://eslint.org/docs/rules/consistent-return) warning.)

🗒️ This PR was previously approved, but I accidentally re-requested it after applying the updates mentioned above (it received the green light to merge following those changes in 1:1 meeting). Additionally, I’ve merged the recent docker-compose.env change (#296), so I’m proceeding to merge this into dev now. Thank you!