[abdul-karim-mia]

When req.session.regenerate() is called prior to req.session.save(), express-session was still resaving the session to the store when the response finished.

Cause

1. wrapmethods only wrapped reload and save. When sess.regenerate replaced req.session with a newly generated session instance, the new instance did not have save or reload wrapped, so calling req.session.save() did not update savedHash.
2. Additionally, originalId retained the old session ID from before regeneration. Because originalId !== sess.id, isSaved(sess) evaluated to false, causing shouldSave(req) to trigger a duplicate save at the end of the request.

Solution

• Wrap sess.regenerate in wrapmethods using rewrapmethods.
• In rewrapmethods, update originalId and originalHash to match the newly generated session, and reset savedHash if the session ID changed.
• Added regression tests for saving regenerated sessions (both default and saveUninitialized: false).

Fixes #935