Fix auth redirect on jwt expiry

[chris-t-li]

This PR starts to address Issue #146

• authentication_controller - added refresh token with 90 day expiry on login and signup. Blacklists refresh token on logout.
• Add autologin route - which tries to authenticate request with token. If that fails, it will try to authenticate with refresh token. If that is successful, return new tokens. If that fails, then return authorized
• JsonWebToken - added jwt_refresh method that generates a refresh token with 90 day expiry

Auth Routes on Client

• Add 404 page not found for any routes that are not defined
• Add tryAutoLogin functions to Authorization and RequireAuth components, which redirects to "/profile" if successful, otherwise redirects to "/auth"
• Created useAutoLoginMutation endpoint

WIP

• still need to test background task of deleting expired blacklisted tokens
• still need to test that JWT is refreshed if token is expired by refresh token is still valid

[netlify[bot]]

✅ Deploy Preview for fantasyfit ready!

Name	Link
🔨 Latest commit	d91e4f75fda270a4d25535284da63d398b5baff6
🔍 Latest deploy log	https://app.netlify.com/sites/fantasyfit/deploys/64776c4b71cbbb000879446d
😎 Deploy Preview	https://deploy-preview-147--fantasyfit.netlify.app/
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[chris-t-li]

Created Issue #149 for handling background task of deleting expired blacklisted tokens

[chris-t-li]

Fixed a semi colon typo that was triggering unauthorized 401.

See line 6 of client/src/store/auth/userSlice.js

[chris-t-li]

Have fixed JWT refresh functionality with latest commit 0452e85

On client side, if baseQuery returns 401 status (because token has expired), client will retry to fetch using refresh token. On rails side, this reaches /auth/refresh endpoint. If refresh token is still valid, generate new tokens and refresh tokens and send back to client.

Still need to test if refresh token is no longer valid.

Also, consider if still need autologin logic as there is duplication here. This addresses issue #146