[backend] Kill session on synchro when an HTTP error is send to client. (#7842)

[aHenryJard]

Proposed changes

• Kill session when an HTTP error is send back because EventSource that is used on syncManager closes the stream automatically on HTTP code that are different from 200 or 300 (redirects).

From my test locally, session flood can happen:

• When remote OCTI stream sever is "running = false"
• When user has not enough rights (marking, capacity or other checks on data)

Related issues

• closes Platform is flooded with sessions when stopping a stream consumed by other remote platforms #7842

Checklist

• I consider the submitted work as finished
• I tested the code for its functionality
• I wrote test cases for the relevant uses case (coverage and e2e)
• I added/update the relevant documentation (either on github or on notion)
• Where necessary I refactored code to improve the overall quality

Further comments

[codecov]

Codecov Report

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

Project coverage is 67.88%. Comparing base (eebee14) to head (46a4086).
Report is 7 commits behind head on master.

Files	Patch %	Lines
...tform/opencti-graphql/src/graphql/sseMiddleware.js	0.00%	32 Missing ⚠️
...latform/opencti-graphql/src/manager/syncManager.js	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7980      +/-   ##
==========================================
- Coverage   67.90%   67.88%   -0.02%     
==========================================
  Files         571      571              
  Lines       70811    70827      +16     
  Branches     6048     6049       +1     
==========================================
- Hits        48082    48080       -2     
- Misses      22729    22747      +18     

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