Add Handling For Access Tokens That Never Expire (ex: GITHUB) - #491

Proposed changes

• Added handling to allow tokens that never expire to be saved properly in db

Github Docs Link: https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation
Stackoverflow Link: https://stackoverflow.com/questions/26902600/whats-the-lifetime-of-github-oauth-api-access-token

Types of changes

What types of changes does your code introduce to Lowcoder?
Put an x in the boxes that apply.

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help!
This is simply a reminder of what we are going to look for before merging your code.
Put an x in the boxes that apply.

• Lint and unit tests pass locally with my changes
• 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

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc.