Make sure we don't reuse an old NSEUserSession after logging out and back in.

[pixlwave]

There have been reports of users receiving blank notifications after upgrading to SSS. Turns out when the user logs out, the NSE isn't aware of this so attempts to re-use the same UserSession/Client from the old session.

This PR fixes it with an additional comparison at the start of the flow.

[github-actions]

	Warnings
⚠️	Some of the commits are missing ticket numbers. Please consider squashing all commits that don't have a tracking number.

Generated by 🚫 Danger Swift against 73e181a

[sonarcloud]

Quality Gate passed

Issues
0 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 SonarCloud

[stefanceriu]

🤦

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.

Project coverage is 77.54%. Comparing base (022cc59) to head (73e181a).
Report is 1 commits behind head on develop.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
NSE/Sources/NotificationServiceExtension.swift	0.00%	3 Missing ⚠️
NSE/Sources/Other/NSEUserSession.swift	0.00%	2 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #3273      +/-   ##
===========================================
+ Coverage    77.51%   77.54%   +0.03%     
===========================================
  Files          725      725              
  Lines        58734    58738       +4     
===========================================
+ Hits         45527    45551      +24     
+ Misses       13207    13187      -20     

Flag	Coverage Δ
unittests	69.00% <0.00%> (+0.03%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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