♻️ Renaming session cookie once again

[GitHK]

What do these changes do?

Apparently Firefox handles cookies differently than Chrome and Safari. It keeps cookies with the same name but different domains.
Even after invalidating the session key for the cookies. You login into Firefox open a new style dynamic service and authentication fails. Apparently it send out old cookie, the one with domain osparc.io (which is invalid) instead of the one with .osparc.io domain. This causes a 401 reply when opening UUID.services.osparc.io.

To avoid issues for users, the session cookie is being renamed.

Related issue/s

• 🎨 Adds authentication for new style dynamic services and platform vendor services ⚠️ #6484

How to test

Dev-ops checklist

• No ENV changes or I properly updated ENV (read the instruction)

[sonarqubecloud]

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.1%. Comparing base (cafbf96) to head (bf40ca7).
Report is 638 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #6544      +/-   ##
=========================================
+ Coverage    84.5%   88.1%    +3.5%     
=========================================
  Files          10    1548    +1538     
  Lines         214   63350   +63136     
  Branches       25    2059    +2034     
=========================================
+ Hits          181   55836   +55655     
- Misses         23    7195    +7172     
- Partials       10     319     +309     

Flag	Coverage Δ
integrationtests	64.7% <ø> (?)
unittests	86.1% <100.0%> (+1.5%)	⬆️

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

Files with missing lines	Coverage Δ
...ings-library/src/settings_library/utils_session.py	44.4% <100.0%> (ø)

... and 1497 files with indirect coverage changes

[YuryHrytsuk]

This will break a few e2e ops tests because we explicitly rely on Cookie name. We need to update these tests as soon as this fix is rolled out.

Furthermore, this needs to be done in stages (master --> stag --> prod)

I will take care of it

[YuryHrytsuk]

This will break a few e2e ops tests because we explicitly rely on Cookie name. We need to update these tests as soon as this fix is rolled out.

Furthermore, this needs to be done in stages (master --> stag --> prod)

I will take care of it

I wonder if there are other places that explicitly rely on this cookie name. I hope there are no such 3rd parties

[GitHK]

This will break a few e2e ops tests because we explicitly rely on Cookie name. We need to update these tests as soon as this fix is rolled out.
Furthermore, this needs to be done in stages (master --> stag --> prod)
I will take care of it

I wonder if there are other places that explicitly rely on this cookie name. I hope there are no such 3rd parties

inside the simcore codebase there are no other places. And we have tests to avoid cookie being out of sync that fail.
regarding other repos I would not know