Change flask-api dependency to upstream develop branch

[ngdio]

For flask-api, the Pipfile points at a branch in a forked repository that no longer exists as it has been merged into upstream, causing pipenv to fail to lock. I've changed it to the upstream development branch which is where the changes can be found and properly installed.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (6677f4a) 70.83% compared to head (9456892) 66.88%.
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #524      +/-   ##
==========================================
- Coverage   70.83%   66.88%   -3.95%     
==========================================
  Files          40       41       +1     
  Lines        2273     2271       -2     
  Branches      338      338              
==========================================
- Hits         1610     1519      -91     
- Misses        556      655      +99     
+ Partials      107       97      -10     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[codders]

Thanks for the PR! It seems like as well as changing the source of flask-api, you also updated the versions of all the other libraries, and in the latest version of pyright we have some new type issues.

If you want to submit a change for just flask-api, that would be very welcome. Otherwise I will look later on about either fixing the pyright issues or just upgrading the one library.

[ngdio]

I understand, will take care of it. Though it might be best to adjust to the Pyright changes as well, keeping it to the original purpose should be good enough for now

[ngdio]

I don't think there is a way to add or change a dependency in pipenv without causing the whole Pipfile.lock to update entirely. I've locked pyright to the previously used version as well as firebase-admin which seems to have had a breaking change, everything else seems to work as previously.

This should be better practice anyway, if there's anything that broke it through this the dependency should be fixed to the version it last worked in.