feat: support maxAgeInMs and fully compatible with express-session on cookie.maxAge

[MaxMEllon]

refs: #369

About

• Add maxAgeInMs option, refs: Session stores expect maxAge to be in milliseconds not seconds #369
• Keeps the internal session.cookie.maxAge in milliseconds so that expire is handled correctly by the express-session store adapter.
• maxAge can be used as before. However, when passing it to the store, maxAge is converted to milliseconds.

Context

connect-dynamodb computes expires by inheriting cookie.maxAge. source
And express-session expects cookie.maxAge to be milliseconds.
next-session is specified in seconds, which causes problems when connect-dynamodb and next-session are used in combination.
This is because next-session is not fully compatible with express-session.
refs: ca98am79/connect-dynamodb#87 (comment)

[changeset-bot]

⚠️ No Changeset found

Latest commit: b420b91

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.19%. Comparing base (5615e7d) to head (b420b91).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #386      +/-   ##
==========================================
+ Coverage   99.17%   99.19%   +0.01%     
==========================================
  Files           6        6              
  Lines         121      124       +3     
  Branches       37       38       +1     
==========================================
+ Hits          120      123       +3     
  Misses          1        1              

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