Update auth cookie logic for both backend and frontend (seamless temp auth)

[spwoodcock]

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation
• 🧑‍💻 Refactor
• ✅ Test
• 🤖 Build or CI
• ❓ Other (please specify)

Related Issue

Follow on from #1948

Describe this PR

• This is the final things to fix prior to new release 2024.5.0.
• Please check over all of my logic & test this thoroughly @Sujanadh @Anuj-Gupta4 @NSUWAL123 @manjitapandey
• I haven't thoroughly tested this yet, as I planned to merge early and test more easily on dev. It's also getting late for me, so I though it best to just push and let you all help me find errors too!

Content

• I removed the 'Temporary Login' card / option from the mapper frontend.
• Now the login is handled seamlessly: if the user is not logged in, they are provided a temporary token/cookie.
• If the user logs in via OSM, they overrides the temp token (temp cookies are revoked).
• We should update at some point to inform the user of this:
  • First load of mapper frontend, we have a localStorage key / prompt.
  • If the user is not signed in via OSM, we say: 'You are not signed in via OSM. If you wish for your mapping contributions to be linked to your profile, please log in first'.
• I made the logic a bit more DRY on the backend.
• The refresh endpoints refresh both cookies, but also return the user details JSON.

Review Guide

Notes for the reviewer. How to test this change?

Checklist before requesting a review

• 📖 Read the FMTM Contributing Guide: https://github.com/hotosm/fmtm/blob/main/CONTRIBUTING.md
• 📖 Read the HOT Code of Conduct: https://docs.hotosm.org/code-of-conduct
• 👷‍♀️ Create small PRs. In most cases, this will be possible.
• ✅ Provide tests for your changes.
• 📝 Use descriptive commit messages.
• 📗 Update any related documentation and include any relevant screenshots.

[optional] What gif best describes this PR or how it makes you feel?

[spwoodcock]

Merging early so this can be tested easily, but please still review + test thoroughly everyone 🙏

When I wake up, if all is well, I will make the release 🎉

[spwoodcock]

On refresh, the json payload was not returning with AuthUser correctly:

Added commit 3a9a50f to address this, now deploying.

Heading to bed, but hopefully it works 🤞 😴

[Anuj-Gupta4]

@spwoodcock
I tried testing and debugging the code. Findings:

The refresh endpoint for mapper worked at first.
Then I cleared all cookies and logged in.
Now the endpoint has stopped working.

If there are no tokens and mapper frontend is accessed:
Refresh mapper looks for mapper login and the authenticate user function throws error saying token not found before the refresh mapper has a chance to set temporary cookies.

Refresh management endpoint also throws error.

Since same functions are being called with different parameters and response is being passed around a lot, the generated response does not always work with other functions and frontend.

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ OperationalError: the connection is closed app.db.models in update View Issue

_{Did you find this useful? React with a 👍 or 👎}

[spwoodcock]

I think the above issue is related to the ones you fixed @Anuj-Gupta4 , but would you be able to double check its not a separate issue? 🙏

[Anuj-Gupta4]

It is the same issue. We changed the code to use separate db pool connection for updating the background task status.