Fix E2EE Session Initialization Race Condition

[shwetd19]

Problem

When enabling E2EE, session initialization can be triggered twice through different paths:

1. Via olmAdapter.initSessions() from setEnabled
2. Via onParticipantPropertyChanged from setLocalParticipantProperty

This causes runtime errors when the second initialization attempt finds an existing session.

Solution

I've created a new E2EESessionManager class that keeps track of all session states in one place. This prevents multiple initialization attempts and handles them more gracefully. When a second initialization is attempted, instead of failing, it either returns the existing session or waits for the ongoing initialization to complete.

Implementation Details

• Uses Map to track session states and initialization promises
• Implements state machine for session lifecycle management
• Provides safe access methods with proper error boundaries
• Integrates with existing OlmAdapter without breaking changes

Related Issues

Fixes #2587 - Runtime error when E2EE is enabled

[shwetd19]

Hey @saghul can you please review my PR as per fix of #2587

[jitsi-jenkins]

Hi, thanks for your contribution!
If you haven't already done so, could you please make sure you sign our CLA (https://jitsi.org/icla for individuals and https://jitsi.org/ccla for corporations)? We would unfortunately be unable to merge your patch unless we have that piece :(.

[shwetd19]

Hey @jitsi-jenkins , I've signed the CLA

[saghul]

Seems to be going in the right direction. I suppose you plan on integrating this into the existing flow?

[shwetd19]

Yes @saghul !

[shwetd19]

Hey @saghul @jitsi-jenkins can you please suggest any changes if required ?

[saghul]

See ths CI failures in GH actions. Also the change is not complete / functional. Nobody is importing or calling the new classes you defined.