fix: modified SessionStateBuilder to use new_from_existing

[gtrawinski]

Description

The description of the main changes of your pull request

Related Issue(s)

Documentation

[rtyler]

👋 seems like a pretty straightforward change, can you share more details on what issue this resolves?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.12%. Comparing base (48cf336) to head (767a87a).
Report is 13 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3496      +/-   ##
==========================================
+ Coverage   71.36%   73.12%   +1.76%     
==========================================
  Files         149      149              
  Lines       44919    44885      -34     
  Branches    44919    44885      -34     
==========================================
+ Hits        32055    32824     +769     
+ Misses      10788     9925     -863     
- Partials     2076     2136      +60     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gtrawinski]

👋 seems like a pretty straightforward change, can you share more details on what issue this resolves?

Sure - the SessionState that's provided in the argument of the method is not being used in the code. That change allows to use the fields from provided SessionState and maintain the consistency. It's similarly implemented for the update command.