fix(getSession): use semaphore lock for unseal operation

[JAD3N]

🔗 Linked issue

#610

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

I've added session locking that will asynchronously block consecutive getSession attempts when unsealing.

This should solve the problem where consecutive getSession calls break session data and prevent duplicate unseals (I tested the changes against the issue's reproduction).

Resolves #610

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (ba275c3) 77.69% compared to head (cfdacf3) 77.79%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #612      +/-   ##
==========================================
+ Coverage   77.69%   77.79%   +0.09%     
==========================================
  Files          47       47              
  Lines        4269     4279      +10     
  Branches      604      609       +5     
==========================================
+ Hits         3317     3329      +12     
+ Misses        935      933       -2     
  Partials       17       17              

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

[pi0]

Thanks for the PR ❤️ I have added tests and few refactors to simplify using same context.sessions for locking.

As a future enhancement, we need to do concurrency/promise-reuse in function level which is currently not possible as updateSession has dependency on getSession promise but it will likely catch other edge case scenarios. (~> #617)