refactor: added helper function performSessionEnd

[jaissica12]

Background

• Session timeout calculations were duplicated in initialize() and endSession() methods
• Both methods checked for session timeout but used different approaches:
  • initialize() used Date object comparison
  • endSession() used millisecond arithmetic with inverted logic
• Session end operations (logging event, clearing data, nullifying session) were scattered inline within endSession()

What Has Changed

• Added performSessionEnd helper - Extracted session end operations into a dedicated function
• Added hasSessionTimedOut helper - Consolidates duplicate session timeout calculation logic

Screenshots/Video

• {Include any screenshots or video demonstrating the new feature or fix, if applicable}

Checklist

• I have performed a self-review of my own code.
• I have made corresponding changes to the documentation.
• I have added tests that prove my fix is effective or that my feature works.
• I have tested this locally.

Additional Notes

• The original code used different comparison operators:
• initialize() used > - session expired after 30:00.000
• endSession() used >= - session expired at 30:00.000

As of now I have standardized on >=, let me know if you think otherwise

Reference Issue (For employees only. Ignore if you are an outside contributor)

• Closes https://go/j/SDKE-376

[sonarqubecloud]

Quality Gate passed

Issues
12 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud